Subject: RE: kern/35054: Panic writing to LFS
To: , <kern-bug-people@netbsd.org>
From: Scott Ellis <scotte@warped.com>
List: netbsd-bugs
Date: 11/15/2006 09:48:12
Well, I just didn't hit 'y' long enough.

Re-running the fsck with '-y' completes after asking 472876 times.  Note in
the fsck_lfs messages below that it claims no space for lost+found, yet the
partition is significantly larger than the data being written to it (it
should have ~100G 'extra' space on the LFS partition).  Re-running fsck
again and again yields the same results.


Additional data from that run, done passing '-d' to fsck_lfs:

** /dev/rraid1h
sb0 857886, sb1 857886** File system is already clean
idaddr    = 0x3c36e8b
dev_bsize = 512
lfs_bsize = 65536
lfs_fsize = 1024
lfs_frag  = 64
lfs_inopb = 8
maxino    = 127764
** Last Mounted on /mounts/drive2
** Phase 0 - Check Inode Free List
** Phase 1 - Check Blocks and Sizes
creating sorted inode address table...
counting dirs...
counting blocks...
** Phase 2 - Check Pathnames
UNALLOCATED  I=70190
PARENT=2
INO is NULL

REMOVE? yes

** Phase 3 - Check Connectivity
UNREF DIR  I=88470  OWNER=scotte MODE=40755
SIZE=1024 MTIME=Nov 14 13:56 2006
RECONNECT? yes

NO lost+found DIRECTORY
CREATE? yes

DIRECTORY ? INO 70190: CONTAINS EMPTY BLOCKS [1]
ADJUST LENGTH? yes

[repeat]

YOU MUST RERUN FSCK AFTERWARDS
SORRY. NO SPACE IN lost+found DIRECTORY

** Phase 4 - Check Reference Counts
** Phase 5 - Check Segment Block Accounting
SEGMENT 23314 CLAIMS 1873280 BYTES BUT HAS 1701248 (HIGH BY 172032)

FIX? yes

SEGMENT 23498 CLAIMS 509696 BYTES BUT HAS 493440 (HIGH BY 16256)

FIX? yes

SEGMENT 23675 CLAIMS 898048 BYTES BUT HAS 756480 (HIGH BY 141568)

FIX? yes

SEGMENT 23807 CLAIMS 1723648 BYTES BUT HAS 1722624 (HIGH BY 1024)

FIX? yes

SEGMENT 23808 CLAIMS 395648 BYTES BUT HAS 394624 (HIGH BY 1024)

FIX? yes

DMETA GIVEN AS 841891, SHOULD BE 997762

FIX? yes

AVAIL GIVEN AS 221461738, SHOULD BE 221305654

FIX? yes

125039 files, 46913874 used, 215478370 free

WRITE CHANGES TO DISK? yes

WRITING CHANGES TO DISK

UPDATE SUPERBLOCKS? yes

writing superblocks with lfs_idaddr = 0x3c36f8e

MARK FILE SYSTEM CLEAN? yes

writing superblocks with lfs_idaddr = 0x3c36f8e

***** FILE SYSTEM MARKED CLEAN *****
buffer cache: 990309 hits 276201 misses (78.19%); hash width 1024, depth 249

***** FILE SYSTEM WAS MODIFIED *****

***** PLEASE RERUN FSCK *****