[lkml]   [2002]   [Sep]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [BK PATCH] Add ext3 indexed directory (htree) support
On Wed, Sep 25, 2002 at 10:23:11PM -0700, Ryan Cumming wrote:
> It seems to be running stable now. Linux 2.4.19, UP Athlon, GCC 3.2.

Just to humor me, can you try it with gcc 2.95.4? I just want to
eliminate one variable....

> 3) While starting man(1), EXT3 began spewing messages in the form:
> "EXT3-fs error (device (ide0(3,2)): ext3_readdir: directory #4243459 contains
> a hole at offset xxxxxx"

what directory was 4243459? You can use the debugfs's ncheck command
to get back a pathname from an inode number?

Are you sure the filesystem was consistent before you started this
whole procedure?

It sounds like you hadn't started modifying directories at this point
in the procedure. Yet this error ("directory #XXXX contains a hole")
is printed by the non-indexed-directory version of readdir. So that
would imply that the directory with the initial error reported on it
was not an indexed directory..... very strange!

> The directory number stayed constant, but the offset was variable. fsck -fD
> had -not- been run at this point.
> 4) On reboot, fsck reported:
> "Directory inode has unallocated block #xx"
> multiple times. fsck seemed to fully recover the filesystem. I rebooted again
> for good measure.

What were the directory inode numbers, and what pathname did they map

> 7) While KDE was trying to start, EXT3 dumped the following to the console:
> "EXT3-fs error (device ide(3,2)) in start_transaction: Journal has aborted"

This message will appear if previously some other part of ext2
reported a filesystem inconsistency. So it's a symptom, and not the
root cause of the problem.

> 8) I rebooted, and fsck said:
> "Directory inode 131073,block3,offset 528: Directory corrupted"
> I wasn't so lucky this time, and a good portion of my home directory got
> eaten.

Against, what was the pathnmae to the inode #131073?

This is strange, since I'm not seeing any of the problems that you're
seeing. I'm going to need a lot more information if I'm going to have
a prayer of a chance of digging into it.

- Ted
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:29    [W:0.073 / U:0.264 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site