On Mon, 9 Dec 2002, Kirk McKusick wrote:
> It appears that you are getting all those errors (BAD block)
> because fsck thinks that your filesystem is smaller than it
> really is. If you do a dumpfs on the filesystem and check
> the size (about line 5), I expect that you will find that
> all those bad blocks exceed that size. It might be interesting
> to check one or more of the alternate blocks to see if they
> have a different size. If so, using an alternate should help.
> If not, then the question is why all those out of range blocks 
> were allocated.

I booted an older kernel (Dec. 4) and ran fsck_ffs -b 32.  It repaired a
few simple errors (summary info bad).  I then copied the alt sblock to the
default location with dd.  I reran fsck to make sure the sblock was copied
correctly and it came up clean.  Everything was fine.

I rebooted into multiuser with the old kernel and everything worked fine.  
I did a full buildkernel with srcs as of yesterday at 5 pm without any bad
block messages.  But after rebooting with that new kernel, it tried to
correct the sblockloc again and my system started having the same problem
again.  uname and dmesg is below.

-Nate

FreeBSD 5.0-CURRENT #1: Mon Dec 16 18:05:56 PST 2002

/: correcting fs_sblockloc from 4 to 8192
bad block 1553167, ino 386832
/usr: optimization changed from TIME to SPACE
bad block 1553152, ino 387421
pid 42 (syncer), uid 0 inumber 387421 on /usr: bad block
bad block 1551181, ino 383169
pid 42 (syncer), uid 0 inumber 383169 on /usr: bad block
bad block 1632087, ino 383281
pid 42 (syncer), uid 0 inumber 383281 on /usr: bad block
bad block 1616355, ino 383200
pid 42 (syncer), uid 0 inumber 383200 on /usr: bad block
bad block 1623472, ino 383200
pid 42 (syncer), uid 0 inumber 383200 on /usr: bad block
bad block 1551227, ino 383200
pid 42 (syncer), uid 0 inumber 383200 on /usr: bad block
bad block 1552592, ino 383200
pid 42 (syncer), uid 0 inumber 383200 on /usr: bad block
bad block 1555160, ino 383200
pid 42 (syncer), uid 0 inumber 383200 on /usr: bad block
bad block 1555208, ino 383200
pid 42 (syncer), uid 0 inumber 383200 on /usr: bad block
bad block 1550776, ino 383200
pid 42 (syncer), uid 0 inumber 383200 on /usr: bad block
bad block 1551208, ino 383198
pid 42 (syncer), uid 0 inumber 383198 on /usr: bad block
bad block 1551209, ino 383241
pid 42 (syncer), uid 0 inumber 383241 on /usr: bad block
bad block 1553153, ino 387219
pid 42 (syncer), uid 0 inumber 387219 on /usr: bad block
bad block 1552704, ino 389415
pid 42 (syncer), uid 0 inumber 389415 on /usr: bad block
bad block 1552707, ino 390100
pid 42 (syncer), uid 0 inumber 390100 on /usr: bad block
bad block 1639665, ino 391119
pid 42 (syncer), uid 0 inumber 391119 on /usr: bad block
bad block 1553170, ino 391111
pid 42 (syncer), uid 0 inumber 391111 on /usr: bad block
bad block 1553431, ino 391118
pid 42 (syncer), uid 0 inumber 391118 on /usr: bad block
bad block 1553405, ino 391122
pid 42 (syncer), uid 0 inumber 391122 on /usr: bad block


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to