For info, I had this as well. Kernel 2.4.19 only. Using e2fsprogs 1.29.
I've not used tune2fs, just using -D switch to e2fsck. Using ext3 on
all filesystems.
No obvious complaints from e2fsck, although I wasn't really watching
it. No entries in /'s lost+found. No problems with other filesystems.
Only lost device files in /dev (about 120) with no discernible pattern.
Mike
dumpe2fs output:
Filesystem volume name: root
Last mounted on: /
Filesystem UUID: 6278d5f9-5583-4651-8d58-f12886a4e3a9
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal dir_index filetype needs_recovery sparse_super
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 122624
Block count: 244991
Reserved block count: 2449
Free blocks: 79421
Free inodes: 86789
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 15328
Inode blocks per group: 479
Last mount time: Thu Oct 31 17:08:15 2002
Last write time: Thu Oct 31 17:08:15 2002
Mount count: 4
Maximum mount count: 31
Last checked: Wed Oct 30 18:57:46 2002
Check interval: 15552000 (6 months)
Next check after: Mon Apr 28 19:57:46 2003
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal UUID: <none>
Journal inode: 8
Journal device: 0x0000
First orphan inode: 0
Default directory hash: tea
Directory Hash Seed: c9f2f715-bc28-4302-a2e9-e53aa08576f7
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/