Messages in this thread | | | Date | Fri, 20 Apr 2007 18:14:47 -0500 | From | Eric Sandeen <> | Subject | Re: [PATCH] fix ext2 allocator overflows above 31 bit blocks |
| |
Andreas Dilger wrote: > 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.
I figure this is in the fine tradition of "enough rope to hang oneself"
If you have 16T of filesystem you probably know enough to not hang yourself this way.
*shrug*
It's a bug, today. If we need another change to limit ext2 to 500G or something, fine by me. :)
-Eric - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |