linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Ryan Cumming <ryan@completely.kicks-ass.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH] Add ext3 indexed directory (htree) support
Date: Thu, 26 Sep 2002 01:57:55 -0400	[thread overview]
Message-ID: <20020926055755.GA5612@think.thunk.org> (raw)
In-Reply-To: <200209252223.13758.ryan@completely.kicks-ass.org>

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
to?

> 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

  reply	other threads:[~2002-09-26  5:53 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-25 20:03 tytso
2002-09-25 20:34 ` Andreas Dilger
2002-09-25 20:41 ` Dave Jones
2002-09-25 21:08   ` Andreas Dilger
2002-09-25 21:34   ` Theodore Ts'o
2002-09-25 22:54 ` Jeff Garzik
2002-09-25 23:29   ` Theodore Ts'o
2002-09-25 23:45     ` Ryan Cumming
2002-09-26  3:27       ` Theodore Ts'o
2002-09-26  5:23         ` Ryan Cumming
2002-09-26  5:57           ` Theodore Ts'o [this message]
2002-09-26  6:22             ` Ryan Cumming
2002-09-26 14:05               ` Theodore Ts'o
2002-09-26  6:25             ` Ryan Cumming
2002-09-26 11:25               ` Daniel Egger
2002-09-26  7:41             ` Ryan Cumming
2002-09-26 13:23               ` Theodore Ts'o
2002-09-26 15:42               ` Theodore Ts'o
2002-09-26 19:08                 ` Ryan Cumming
2002-09-26 19:51                   ` Horst von Brand
2002-09-26 19:59                     ` Ryan Cumming
2002-09-26 22:04                   ` Theodore Ts'o
2002-09-26 22:53                     ` Ryan Cumming
2002-09-26 23:57                       ` Theodore Ts'o
2002-09-27  1:00                         ` Ryan Cumming
2002-09-27  3:24                           ` Theodore Ts'o
2002-09-27  4:12                         ` Andreas Dilger
2002-09-27  7:55                           ` Ryan Cumming
2002-09-28  1:20                           ` Ryan Cumming
2002-09-28  1:46                             ` Ryan Cumming
2002-09-28 14:13                             ` Theodore Ts'o
2002-09-28 14:18                               ` Theodore Ts'o
2002-09-28 22:35                                 ` Ryan Cumming
2002-09-28 17:27                               ` [Ext2-devel] " Andreas Dilger
2002-09-28 18:43                                 ` chrisl
2002-09-28 19:45                                 ` chrisl
2002-09-28 22:30                               ` Ryan Cumming
2002-09-29  7:03                               ` [PATCH] fix htree dir corrupt after fsck -fD chrisl
2002-09-29  8:16                                 ` Ryan Cumming
2002-09-29  8:36                                   ` Ryan Cumming
2002-09-30  2:46                                   ` Ryan Cumming
2002-09-29 14:13                                 ` Theodore Ts'o
2002-09-25 23:31 ` [BK PATCH] Add ext3 indexed directory (htree) support Daniel Egger
2002-09-26  0:32   ` Randy.Dunlap
2002-09-26  0:50 ` Aaron Lehmann
2002-09-26  3:28   ` Theodore Ts'o
2002-10-02  9:11 tytso

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020926055755.GA5612@think.thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ryan@completely.kicks-ass.org \
    --subject='Re: [BK PATCH] Add ext3 indexed directory (htree) support' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).