|| ||Mingming Cao <email@example.com>|
|| ||Andrew Morton <firstname.lastname@example.org>|
|| ||[RFC][PATCH 0/2]Extend ext3 filesystem limit from 8TB to 16TB|
|| ||Wed, 29 Mar 2006 17:38:50 -0800|
|| ||Takashi Sato <email@example.com>,
Laurent Vivier <Laurent.Vivier@bull.net>,
There are places in ext3 code to use "int" to represent block numbers in
kernel(not on-disk). This seems the "only" reason that why we can only
have 8TB ext3 rather than 16TB. Most times it just a bug with no
particular reason why not use unsigned 32 bit value, so the fix is easy.
However, it is not so straightforward fix for the ext3 block allocation
code, as ext3_new_block() returns a block number, and "-1" to indicating
block allocation failure. Ext3 block reservation code, called by
ext3_new_block(), thus also use "int" for block numbers in some places.
The following patches fixed both the ext3 block allocation code, as well
as the simple ones.
This work is inspired by Takashi's extend ext2/3 file/filesystem
limitation work, but rather, it focus on ext3 filesystem limit only, and
fixed the block allocation/reservation code to support in-kernel 2**32
block number. Also thanks to Laurent for his review.
Have verified these two patches on a 64 bit machine with 10TB ext3
filesystem, fsx runs fine for a few hours. Also testes on 32 bit machine
with <8TB ext3.
Please review this patches and I appreciate comments.
The things need to be done to complete this work is the issue with
current percpu counter, which could not handle u32 type count well.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/