linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* htree indexing and 64-bit file systems
@ 2009-02-03 22:22 Valerie Aurora Henson
  2009-02-03 23:31 ` Theodore Tso
  0 siblings, 1 reply; 4+ messages in thread
From: Valerie Aurora Henson @ 2009-02-03 22:22 UTC (permalink / raw)
  To: linux-ext4; +Cc: Theodore Tso, Andreas Dilger

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?

-VAL

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: htree indexing and 64-bit file systems
  2009-02-03 22:22 htree indexing and 64-bit file systems Valerie Aurora Henson
@ 2009-02-03 23:31 ` Theodore Tso
  2009-02-07 13:06   ` Goswin von Brederlow
  0 siblings, 1 reply; 4+ messages in thread
From: Theodore Tso @ 2009-02-03 23:31 UTC (permalink / raw)
  To: Valerie Aurora Henson; +Cc: linux-ext4, Andreas Dilger

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: htree indexing and 64-bit file systems
  2009-02-03 23:31 ` Theodore Tso
@ 2009-02-07 13:06   ` Goswin von Brederlow
  2009-02-07 15:54     ` Theodore Tso
  0 siblings, 1 reply; 4+ messages in thread
From: Goswin von Brederlow @ 2009-02-07 13:06 UTC (permalink / raw)
  To: linux-ext4

Theodore Tso <tytso@mit.edu> writes:

> 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

What if the directory is REALLY HUGE? :) Say >68.719.476.736 files.

Can ext4 64bit have directories >8TiB?

MfG
        Goswin

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: htree indexing and 64-bit file systems
  2009-02-07 13:06   ` Goswin von Brederlow
@ 2009-02-07 15:54     ` Theodore Tso
  0 siblings, 0 replies; 4+ messages in thread
From: Theodore Tso @ 2009-02-07 15:54 UTC (permalink / raw)
  To: Goswin von Brederlow; +Cc: linux-ext4

On Sat, Feb 07, 2009 at 02:06:56PM +0100, Goswin von Brederlow wrote:
> What if the directory is REALLY HUGE? :) Say >68.719.476.736 files.
> 
> Can ext4 64bit have directories >8TiB?

No, ext4 directories are limited to 2TB.  Htree directories are
currently limited to a depth of two, which for smaller block sizes
will be more of limitation than the maximum size limitation.

     	     		   	    	    - Ted

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2009-02-07 17:26 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-02-03 22:22 htree indexing and 64-bit file systems Valerie Aurora Henson
2009-02-03 23:31 ` Theodore Tso
2009-02-07 13:06   ` Goswin von Brederlow
2009-02-07 15:54     ` Theodore Tso

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).