public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "LIOU Payphone" <lioupayphone@gmail.com>
To: "'Theodore Tso'" <tytso@mit.edu>
Cc: <linux-ext4@vger.kernel.org>
Subject: Re: ask for help; hash-directory machanism of ext3 cannot work well
Date: Fri, 22 Jun 2007 09:52:55 +0800	[thread overview]
Message-ID: <467b2b7b.0f98600a.1bbc.ffff9c53@mx.google.com> (raw)
In-Reply-To: <20070621165749.GA5664@thunk.org>

Hello, Ted. I think I failed to represent it very well. But many thanks. :-)

What makes me puzzled is there are two entries both  named  "3220" with ino
"3350" were shown under "/mnt" when I "ls  -li  /mnt".
The version of kernel is 2.6.17-1.2142; and e2fsprogs-1.28. 
You know that we can set "s_def_hash_version" to be "DX_HASH_LEAGCY" in
function  "main{}" of mke2fs.c 
But I don't know why the latest version e2fsprogs-1.39 takes "DX_HASH_TEA"
for default. Why "DX_HASH_LEAGCY" cannot be taken for default? Could you
tell me the reason for it? Thanks.  :-)

------
On Thu, Jun 21, 2007 at 04:40:55PM +0800, LIOU Payphone wrote:
> 
> my problem :

First of all, what version of e2fsprogs and kernel are you using?n

> (1) when i want to format /dev/sda1 to be ext3-filesystem, i  set
> "s_def_hash_version" of "struct ext3_super_block" to be "DX_HASH_LEGACY".
> when the filesystem was formatted successfully, i mounted it under a
> directory named "/mnt". 

How did you set the s_def_hash_version?   Were you using debugfs?

And did you turn on the dir_index feature?  

With recent versions of e2fsprogs the dir_index feature is enabled
default, with DX_HASH_TEA as the default.

> (2) subsequently, i created 40000 empty regular-files under "/mnt" named
> from "0" to "39999".
> (3) then , "ls -li  /mnt" was executed; i saw a puzzling thing : there are
> two indentical entries under the directory named "mnt"!  both inode->i_ino
and
> filename are in the same. The filename is 3220 and ino 3350

Huh?  What do you mean by that?  Are you seeing two entries named
"mnt" in the /mnt directory?   I wasn't able to reproduce this.

> 32203 -rwxrwxrwx 1 liupf liupf 0 Jun 14 11:37 24010
> 32204 -rwxrwxrwx 1 liupf liupf 0 Jun 14 11:37 24011
> 32205 -rwxrwxrwx 1 liupf liupf 0 Jun 14 11:37 24012
> 32206 -rwxrwxrwx 1 liupf liupf 0 Jun 14 11:37 24013 
> 32207 -rwxrwxrwx 1 liupf liupf 0 Jun 14 11:37 24014
> 32208 -rwxrwxrwx 1 liupf liupf 0 Jun 14 11:37 24015
> 32209 -rwxrwxrwx 1 liupf liupf 0 Jun 14 11:37 24016
> 33220 -rwxrwxrwx 1 liupf liupf 0 Jun 14 11:37 25027
> 3220 -rwxrwxrwx 1 liupf liupf 0 Jun 14 11:31 3090
> 3350 -rwxrwxrwx 1 liupf liupf 0 Jun 14 11:31 3220
> 3350 -rwxrwxrwx 1 liupf liupf 0 Jun 14 11:31 3220

You didn't list any "mnt" entries above.  So I don't know what you saw.

						- Ted

  reply	other threads:[~2007-06-22  1:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-21  8:40 ask for help; hash-directory machanism of ext3 cannot work well LIOU Payphone
2007-06-21 16:57 ` Theodore Tso
2007-06-22  1:52   ` LIOU Payphone [this message]
2007-06-22  6:20     ` 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=467b2b7b.0f98600a.1bbc.ffff9c53@mx.google.com \
    --to=lioupayphone@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