"Jose R. Santos" <jrs@xxxxxxxxxx> writes:
> On Fri, 18 Jul 2008 13:35:32 +0200
> Goswin von Brederlow <goswin-v-b@xxxxxx> wrote:
>
>> "Jose R. Santos" <jrs@xxxxxxxxxx> writes:
>>
>> > Hi folks,
>> >
>> > I'm posting a new version of the 64-bit mke2fs patch since it was broken
>> > in many ways (many thanks to Goswin for having a look and pointing them
>> > out). This one can actually handle large fs as runs until its time to
>> > allocate table (where it barfs due bitmap issues). To make 64bit fs, I
>> > use the following command.
>> >
>> > mke2fs -T ext4dev -O64bit /dev/my_large_disk
>>
>> Just like ext2/3 default to a 4k blocksize if it exceeds 2^32 1k
>> blocks shouldn't ext4 default to 64bit if it exceeds 2^32 4k blocks?
>
> Eventually, when the feature is stable enough, we can change the
> default in mke2fs.conf to include this feature for the ext4 fs_type.
> The problem of setting it only if the fs exceeds 2^32 blocks is that
> you will not be able to resize an fs from 32 to 64bit due to the block
> group descriptor size change. Once the feature is stable, it should
> set as default regardless of the storage size.
Won't tune2fs be able to adjust the descriptor size? I thought all the
keeping compatibility with ext2/3 was so people could upgrade without
reformating. Or is that maxime broken with 64bit support?
MfG
Goswin
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
