[Fwd: e2fsck Segmentation Fault]
Tom Coleman
tom at thesnail.org
Mon Jul 25 23:50:02 UTC 2005
Hi,
Somehow I've managed to get e2fsck to seg fault.. The filesystem in
question started acting very strangely (e.g. filenames changing from
music to MuSiC etc) so I rebooted, and since when fsck has crashed every
time it has been run.
I'm not really sure what any of this means, so I didn't know what
debugging output to include, but below is the output of e2fsck.
(I would have attached the results of dumpe2fs, but the mailing list complained).
Thanks for any help; let me know any more information I can provide
(I am running debian unstable with a new (2.6.11-ac) kernel (although it
segfaulted on an older kernel too))
e2fsck output:
e2fsck 1.38 (30-Jun-2005)
/dev/hde1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Root inode is not a directory. Clear? yes
Pass 2: Checking directory structure
Entry '..' in ??? (1785857) has deleted/unused inode 12. Clear? yes
Missing '..' in directory inode 2162689.
Fix? yes
Entry '..' in ... (2162689) has deleted/unused inode 2. Clear? yes
Missing '..' in directory inode 3129345.
Fix? yes
Entry '..' in ... (3129345) has deleted/unused inode 2. Clear? yes
Entry '..' in ??? (5931009) has deleted/unused inode 12. Clear? yes
Missing '..' in directory inode 8601601.
Fix? yes
Entry '..' in ... (8601601) has deleted/unused inode 2. Clear? yes
Pass 3: Checking directory connectivity
Root inode not allocated. Allocate? yes
Unconnected directory inode 5931009 (...)
Connect to /lost+found? yes
/lost+found not found. Create? yes
Unconnected directory inode 1785857 (...)
Connect to /lost+found? yes
Unconnected directory inode 2162689 (...)
Connect to /lost+found? yes
Unconnected directory inode 3129345 (...)
Connect to /lost+found? yes
Unconnected directory inode 8601601 (...)
Connect to /lost+found? yes
Pass 4: Checking reference counts
i_file_acl for inode 11 (...) is 536879104, should be zero.
Clear? yes
i_faddr for inode 11 (...) is 536879104, should be zero.
Clear? yes
i_fsize for inode 11 (...) is 32, should be zero.
Clear? yes
Segmentation fault
More information about the Ext3-users
mailing list