Date: Fri, 12 Jul 2002 10:21:12 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: iedowse@maths.tcd.ie Cc: dschultz@uclink.Berkeley.EDU, current@FreeBSD.ORG Subject: Re: -CURRENT trashes disk label Message-ID: <20020712.102112.89131264.imp@bsdimp.com> In-Reply-To: <200207110902.aa74600@salmon.maths.tcd.ie> References: <20020711074618.GA382@HAL9000.wox.org> <200207110902.aa74600@salmon.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <200207110902.aa74600@salmon.maths.tcd.ie>
Ian Dowse <iedowse@maths.tcd.ie> writes:
: In message <20020711074618.GA382@HAL9000.wox.org>, 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 majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020712.102112.89131264.imp>