From crtb@cape.com  Sun Sep 19 23:07:19 2004
Return-Path: <crtb@cape.com>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C374116A4CE
	for <FreeBSD-gnats-submit@FreeBSD.org>; Sun, 19 Sep 2004 23:07:19 +0000 (GMT)
Received: from mx5.cape.com (mx5.cape.com [204.107.252.38])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 43DAD43D45
	for <FreeBSD-gnats-submit@FreeBSD.org>; Sun, 19 Sep 2004 23:07:19 +0000 (GMT)
	(envelope-from crtb@cape.com)
Received: from tomato ([10.100.102.24])
	by mx5.cape.com (8.12.10/8.12.3) with ESMTP id i8JN7H5A021164;
	Sun, 19 Sep 2004 19:07:18 -0400
Message-Id: <20040919190455.I75932-100000@tomato.local>
Date: Sun, 19 Sep 2004 19:07:17 -0400 (EDT)
From: Charles Bacon <crtb@cape.com>
To: FreeBSD-gnats-submit@FreeBSD.org
Cc: Chuck Bacon <crtb@cape.com>
Subject: 4.5 disklabel gets damaged when mounted by 5.2.1-R

>Number:         71918
>Category:       kern
>Synopsis:       4.5 disklabel gets damaged when mounted by 5.2.1-R
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Sep 19 23:10:22 GMT 2004
>Closed-Date:    Wed May 10 15:07:19 GMT 2006
>Last-Modified:  Wed May 10 15:07:19 GMT 2006
>Originator:     Chuck Bacon
>Release:        FreeBSD 5.2.1-RELEASE i386
>Organization:
none
>Environment:
FreeBSD daisy.local 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE #0: Mon Feb 23 20:45:55 GMT 2004     root@wv1u.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC  i386

	(see uname -a above)
>Description:
	Making a new 5.2.1-R slice on an existing 4.5-R system.  Installation
	and boot OK, mount existing 4.5-R filesystems under 5.2.1-R also OK.
	Trouble when booting from 4.5-R on same disk, complaint of bad boot
	block.  Hunting for superblocks succeeds in restoring 4.5-R FS.
	Note UFS1-UFS2 distinction irrelevant here.
>How-To-Repeat:
	1. Create and then boot a 5.2.1-R partition on an otherwise 4.x disk
	2. Mount, then umount, a 4.x partition on the running 5.2.1-R system.
	3. Shutdown -r and now, boot the 4.x OS.
	4. Mount the 4.x partition previously mounted under 5.2.1-R (or try!)
>Fix:
	Sorry, I'm not very smart about fdisk/disklabel/bsdlabel etc.
>Release-Note:
>Audit-Trail:

From: Maxim Konovalov <maxim@macomnet.ru>
To: Chuck Bacon <crtb@cape.com>
Cc: bug-followup@freebsd.org
Subject: kern/71918
Date: Fri, 14 Apr 2006 01:56:42 +0400 (MSD)

 Hello,
 
 I have a couple of dual (RELENG_4|RELENG_6) boot boxes and never seen
 the problems with mangled boot block/slices/disklabels.  Are you sure
 that was not a some sort of misconfiguration on your side?  Is it
 possible to check the issue with 6.0-RELEASE?
 
 -- 
 Maxim Konovalov
State-Changed-From-To: open->closed 
State-Changed-By: maxim 
State-Changed-When: Wed May 10 15:05:22 UTC 2006 
State-Changed-Why:  
I can't reproduce the problem and the submitter doesn't have 
dual boot environment any more. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=71918 
>Unformatted:
 >Comment:
 	It's been some months, and this box is now all 5.2.1-R, since I have
 	an ATI AGP RADEON board, unknown to the X subsystem on 4.5-R.
 	I may have the details wrong, such as disklabel; I may have used
 	a different approach to restore.
 
