| title: | Re FSCK of corrupted ext3 filesystem |
|
On Fri, Aug 26, 2005 at 01:16:34PM +0100, Matt Bernstein wrote:
On Aug 25 Stephen C. Tweedie wrote:
Which version of e2fsprogs? There were some serious algorithmic
inefficiencies in some really old versions that could explain this sort
of thing.
e2fsprogs-1.37-4 from Fedora Core 4 x86_64.
On Aug 25 Theodore Tso wrote:
What sort of messages was e2fsck printing beforehand?
Nothing I found overly unusual. A few errors in pass 1; it reached the
"checking directory structure" pass (pass 2 IIRC) and then nothing.
I guess at this point I should confess that the filesystem had (as now
Ive trashed it again with mkfs) of the order of hundreds of millions of
directory entries, and tens of millions of inodes.
All in one directory? How may directory entries in a single directory
inode, would you estimate?
If this happens again, where you see no activity for more than say an
hour (either on the console or on the disk drive), please consider
forcing a core dump and sending me the dump along with the e2fsck
binary and the distribution/rpm version of e2fsprogs on the system.
Id be very much interestedin getting to the bototm of this if it
happens again.
Regards,
- Ted
_______________________________________________
Ext3-users@xxxxxxxxxx
rel="nofollow" www.redhat.com/mailman/listinfo/ext3-users www.redhat.com/mailman/listinfo/ext3-users
|
