From: "Tejas Sumant" <tejas.sumant@gmail.com>
To: "Theodore Tso" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Couple of queries related to htree directory
Date: Fri, 15 Jun 2007 16:30:02 +0530 [thread overview]
Message-ID: <ffa0f8300706150400u39c31a13l2805f4d8217eb4cf@mail.gmail.com> (raw)
In-Reply-To: <20070614184630.GB14911@thunk.org>
Hi Theodore,
My file system has dir_index feature.
When I created new directory larger than blocksize and run htree
command of debugfs on it, I received message that the directory is not
in htree format.
Any idea why this happened?
Thanks
On 6/15/07, Theodore Tso <tytso@mit.edu> wrote:
> On Thu, Jun 14, 2007 at 06:52:01PM +0530, Tejas Sumant wrote:
> >
> > Any idea, how to search a directory on given ext3 file system, which
> > is having htree structure?
>
> The same way you search any other Linux/Unix system. I.e., using
> opendir()/readir() from a C program, or /bin/ls from a shell program,
> etc. It's completely transparent.
>
> > Also is there any way to create a htree indexed directory explicitly?
> > using some command or tool?
>
> Once the dir_index feature is enabled, for all new directories and all
> directories which are only take one disk block grow to bigger than one
> disk block, they automatically get indexed. (There's no point
> indexing a single directory block since that's equivalent to a single
> leaf block.)
>
> To convert existing directories, you need to unmount the filesystem
> and use the command:
>
> e2fsck -fD /dev/hdXX
>
> This really should be added to an FAQ on ext4.wiki.kernel.org....
>
> - Ted
>
--
Tejas Sumant
next prev parent reply other threads:[~2007-06-15 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 13:22 Couple of queries related to htree directory Tejas Sumant
2007-06-14 18:46 ` Theodore Tso
2007-06-15 11:00 ` Tejas Sumant [this message]
2007-06-15 16:32 ` Theodore Tso
2007-06-18 2:15 ` Tejas Sumant
2007-06-18 9:13 ` Tejas Sumant
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=ffa0f8300706150400u39c31a13l2805f4d8217eb4cf@mail.gmail.com \
--to=tejas.sumant@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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