Re: -CURRENT trashes disk label
In message: [EMAIL PROTECTED] Ian Dowse [EMAIL PROTECTED] writes: : In message [EMAIL PROTECTED], David Schultz writes: : I just made world on -CURRENT (cvsup a few hours ago), booted : using a new GENERIC kernel and ran mergemaster. Before I : installed world, I mounted the root partition for my more stable : development environment (4.6-RELEASE) to copy my firewall rules : over. In summary: : : # fsck /dev/ad1s1a : ** /dev/ad1s1a : BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE : /dev/ad1s1a: INCOMPLETE LABEL: type 4.2BSD fsize 0, frag 0, cpg 0, size 524288 : : You just need to fsck -b16 /dev/ad1s1a, or alternatively upgrade : to the latest -STABLE fsck, which fixes this issue. There are a few : new superblock fields in use in -CURRENT that trigger some unnecessary : fsck sanity checks. : : The other thing that causes scary-looking errors when moving disks : back and forth between -CURRENT and -STABLE is when the snapshot : used by -CURRENT's fsck gets left behind if you reboot during the : background fsck and then boot -STABLE. Damn. I forgot to include Kirk's UPDATING entry that he sent me on this topic. Sorry about that. I'll deal later today. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
-CURRENT trashes disk label
I just made world on -CURRENT (cvsup a few hours ago), booted using a new GENERIC kernel and ran mergemaster. Before I installed world, I mounted the root partition for my more stable development environment (4.6-RELEASE) to copy my firewall rules over. In summary: # mount /dev/ad1s1a /mnt # mount -ur /mnt# Oops...wanted r/o # cp /mnt/etc/rc.firewall /etc/rc.firewall # umount /mnt # cd /usr/src make installworld I rebooted cleanly a little while later. The next time I booted into 4.6-RELEASE, fsck was very unhappy. # fsck /dev/ad1s1a ** /dev/ad1s1a BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE /dev/ad1s1a: INCOMPLETE LABEL: type 4.2BSD fsize 0, frag 0, cpg 0, size 524288 # fsdb /dev/ad1s1a ** /dev/ad1s1a BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE /dev/ad1s1a: INCOMPLETE LABEL: type 4.2BSD fsize 0, frag 0, cpg 0, size 524288 fsdb: cannot set up file system `/dev/ad1s1a' # disklabel /dev/ad1s1 # /dev/ad1s1: [snip] 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 52428804.2BSD0 0 0 # (Cyl.0 - 32*) b: 524288 524288 swap# (Cyl. 32*- 65*) c: 352304820unused0 0 # (Cyl.0 - 2192*) e: 524288 10485764.2BSD0 0 0 # (Cyl. 65*- 97*) f: 524288 15728644.2BSD0 0 0 # (Cyl. 97*- 130*) g: 21504000 20971524.2BSD0 0 0 # (Cyl. 130*- 1469*) h: 11629330 236011524.2BSD0 0 0 # (Cyl. 1469*- 2192*) I can still mount the partition and it seems to be fine. Did this have something to do with the two seconds that the partition was mounted r/w? I suspect that relabeling the slice will fix the problem, but what went wrong? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: -CURRENT trashes disk label
In message [EMAIL PROTECTED], David Schultz writes: I just made world on -CURRENT (cvsup a few hours ago), booted using a new GENERIC kernel and ran mergemaster. Before I installed world, I mounted the root partition for my more stable development environment (4.6-RELEASE) to copy my firewall rules over. In summary: # fsck /dev/ad1s1a ** /dev/ad1s1a BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE /dev/ad1s1a: INCOMPLETE LABEL: type 4.2BSD fsize 0, frag 0, cpg 0, size 524288 You just need to fsck -b16 /dev/ad1s1a, or alternatively upgrade to the latest -STABLE fsck, which fixes this issue. There are a few new superblock fields in use in -CURRENT that trigger some unnecessary fsck sanity checks. The other thing that causes scary-looking errors when moving disks back and forth between -CURRENT and -STABLE is when the snapshot used by -CURRENT's fsck gets left behind if you reboot during the background fsck and then boot -STABLE. Ian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: -CURRENT trashes disk label
Thus spake Ian Dowse [EMAIL PROTECTED]: In message [EMAIL PROTECTED], David Schultz writes: I just made world on -CURRENT (cvsup a few hours ago), booted using a new GENERIC kernel and ran mergemaster. Before I installed world, I mounted the root partition for my more stable development environment (4.6-RELEASE) to copy my firewall rules over. In summary: # fsck /dev/ad1s1a ** /dev/ad1s1a BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE /dev/ad1s1a: INCOMPLETE LABEL: type 4.2BSD fsize 0, frag 0, cpg 0, size 524288 You just need to fsck -b16 /dev/ad1s1a, or alternatively upgrade to the latest -STABLE fsck, which fixes this issue. There are a few new superblock fields in use in -CURRENT that trigger some unnecessary fsck sanity checks. Excellent, upgrading fsck did the trick. Thanks for the quick reply! (By the way, shouldn't fsdb still work, even if it's confused? If a superblock glitch makes it refuse to start, that sort of defeats the purpose.) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
