From: Theodore Tso <tytso@mit.edu>
To: Valerie Aurora Henson <vaurora@redhat.com>
Cc: linux-ext4@vger.kernel.org, Andreas Dilger <adilger@sun.com>
Subject: Re: htree indexing and 64-bit file systems
Date: Tue, 3 Feb 2009 18:31:08 -0500 [thread overview]
Message-ID: <20090203233108.GW14762@mit.edu> (raw)
In-Reply-To: <20090203222202.GK20654@shell>
On Tue, Feb 03, 2009 at 05:22:02PM -0500, Valerie Aurora Henson wrote:
> I've just been ignoring htree indexing for now, but the regression
> failure in Ted's rebased 64bit tree looks suspiciously htree-related.
>
> What's the interaction between htree and 64 bit file systems? What
> needs to change, if anything?
There shouldn't be any. The block numbers used in htree are logical
block numbers (i.e., block 0 is the first block in the directory,
block 1 is the 2nd block i the directory, etc.)
- Ted
next prev parent reply other threads:[~2009-02-03 23:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 22:22 htree indexing and 64-bit file systems Valerie Aurora Henson
2009-02-03 23:31 ` Theodore Tso [this message]
2009-02-07 13:06 ` Goswin von Brederlow
2009-02-07 15:54 ` 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=20090203233108.GW14762@mit.edu \
--to=tytso@mit.edu \
--cc=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=vaurora@redhat.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;
as well as URLs for NNTP newsgroup(s).