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
