[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGJTRchJ4Mq5in0nXeeF8mA2A=yub7kv4OohUb_QpKtEKCWM-A@mail.gmail.com>
Date: Sun, 21 Jul 2013 19:44:12 -0500
From: Michael <mike@...ftx.net>
To: "H. Peter Anvin" <hpa@...or.com>, Michael <mike@...ftx.net>,
"Theodore Ts'o" <tytso@....edu>, linux-ext4@...r.kernel.org
Subject: Re: EXT4 Larger Than 16TB
Also, in /etc/mke2fs.conf(Ubuntu has this by default):
ext4 = {
features =
has_journal,extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize
auto_64-bit_support = 1
inode_size = 256
}
ext4dev = {
features =
has_journal,extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize
inode_size = 256
options = test_fs=1
}
Also, any info on how to find out if my fs is 64 bit or not? I don't
know what this config was back when I made the system.
On Sun, Jul 21, 2013 at 6:43 PM, Zheng Liu <gnehzuil.liu@...il.com> wrote:
> On Sun, Jul 21, 2013 at 03:47:04PM -0700, H. Peter Anvin wrote:
>> On 07/09/2013 06:45 AM, Michael wrote:
>> > No problem, it sounds like it would be a very tricky bit of code to
>> > write. Shuffling metadata blocks is not an easy feat.
>> >
>> > Is there any way to tell if I'm using 64 bit? Ubuntu defaults to
>> > setting ext4 to default, but I don't know if it did when I first
>> > created this FS.
>> >
>> > If it is 64 bit, the resize2fs utility should be able to handle this
>> > one kernels >3.7, correct?
>> >
>>
>> Is there a way to force this at mkfs time? I.e. "I know I may want to
>> expand this filesystem beyond the 16 TB point?"
>
> Hi Peter,
>
> You could use 'mkfs.ext4 -O 64bit' to force enable 64bit support. In
> addition, we will enable this feature by default. Lukas has a patch to
> fix it. Here is the link [1].
>
> 1. http://patchwork.ozlabs.org/patch/253234/
>
> Regards,
> - Zheng
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists