From: tytso@mit.edu
To: Evgeniy Ivanov <lolkaantimat@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Question about e2fsck and HTree
Date: Fri, 23 Apr 2010 20:45:44 -0400 [thread overview]
Message-ID: <20100424004544.GM14986@thunk.org> (raw)
In-Reply-To: <z2ne1e08eb01004221243m89a97acei72316abe62daaba@mail.gmail.com>
On Thu, Apr 22, 2010 at 11:43:30PM +0400, Evgeniy Ivanov wrote:
> Hello,
>
> I have a question about ext2/ext3.
>
> As I understand directory indexing is compatible feature, currently my
> implementations doesn't support HTree.
> I do some things (make kernel and libs) with FS and check it with
> e2fsck: it creates index (everything else is ok, exit status is 1).
> Then I do same things with FS and check again:
>
> HTree directory inode 23316 has an invalid root node.
>
> Is it OK for implementation without directory indexing?
If your implementation of extN don't support HTree, then it's
important that when you modify a filesystem you clear the inode's
EXT2_INDEX_FL flag. Then the right thing will happen....
- Ted
next prev parent reply other threads:[~2010-04-24 0:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 19:43 Question about e2fsck and HTree Evgeniy Ivanov
2010-04-24 0:45 ` tytso [this message]
2010-04-25 22:10 ` Evgeniy Ivanov
2010-04-25 22:33 ` Theodore Tso
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=20100424004544.GM14986@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=lolkaantimat@gmail.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox