Re: [PATCH] fix ext2 allocator overflows above 31 bit blocks

On Apr 20, 2007  12:10 -0500, Eric Sandeen wrote:
> If ext3 can do 16T, ext2 probably should be able to as well.
> There are still "int" block containers in the block allocation path
> that need to be fixed up.

Yeah, but who wants to do 16TB e2fsck on every boot?  I think there
needs to be some limits imposed for the sake of usability.

Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [PATCH] fix ext2 allocator overflows above 31 bit blocks
  - From: Eric Sandeen <[email protected]>

References:
- [PATCH] fix ext2 allocator overflows above 31 bit blocks
  - From: Eric Sandeen <[email protected]>

Prev by Date: [RFC PATCH 3/3] x86: use the x86 CPU feature API
Next by Date: Re: [PATCH] NET: Add packet sock option to return orig_dev to userspace when bonded
Previous by thread: [PATCH] fix ext2 allocator overflows above 31 bit blocks
Next by thread: Re: [PATCH] fix ext2 allocator overflows above 31 bit blocks
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]