Bug 71918

Summary: 4.5 disklabel gets damaged when mounted by 5.2.1-R
Product: Base System Reporter: Chaeles Bacon <crtb>
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me CC: crtb
Priority: Normal    
Version: 5.2.1-RELEASE   
Hardware: Any   
OS: Any   

Description Chaeles Bacon 2004-09-20 00:10:22 UTC 
	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.

Fix: 

Sorry, I'm not very smart about fdisk/disklabel/bsdlabel etc.
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!)
Comment 1 Maxim Konovalov 2006-04-13 22:56:42 UTC 
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
Comment 2 Maxim Konovalov freebsd_committer freebsd_triage 2006-05-10 16:05:22 UTC 
State Changed
From-To: open->closed

I can't reproduce the problem and the submitter doesn't have 
dual boot environment any more.