Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 11 Jul 2002 00:46:18 -0700
From:      David Schultz <dschultz@uclink.Berkeley.EDU>
To:        current@FreeBSD.ORG
Subject:   -CURRENT trashes disk label
Message-ID:  <20020711074618.GA382@HAL9000.wox.org>

next in thread | raw e-mail | index | archive | help
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   offset    fstype   [fsize bsize bps/cpg]
  a:   524288        0    4.2BSD        0     0     0   # (Cyl.    0 - 32*)
  b:   524288   524288      swap                        # (Cyl.   32*- 65*)
  c: 35230482        0    unused        0     0         # (Cyl.    0 - 2192*)
  e:   524288  1048576    4.2BSD        0     0     0   # (Cyl.   65*- 97*)
  f:   524288  1572864    4.2BSD        0     0     0   # (Cyl.   97*- 130*)
  g: 21504000  2097152    4.2BSD        0     0     0   # (Cyl.  130*- 1469*)
  h: 11629330 23601152    4.2BSD        0     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 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?20020711074618.GA382>