[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4798BD91.20108@redhat.com>
Date: Thu, 24 Jan 2008 10:32:17 -0600
From: Eric Sandeen <sandeen@...hat.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>,
"Theodore Ts'o" <tytso@....edu>, Mingming Cao <cmm@...ibm.com>,
"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: Patch queue update
Andreas Dilger wrote:
> On Jan 24, 2008 20:20 +0530, Aneesh Kumar K.V wrote:
>> @@ -89,6 +89,8 @@ When mounting an ext4 filesystem, the following option are accepted:
>> extents ext4 will use extents to address file data. The
>> file system will no longer be mountable by ext3.
>>
>> +noextents ext4 will not use extents for new files created.
>> +
>
> s/new files created/newly created files/
Would a blurb about keeping ext3 disk-format compatibility be worthwhile
here?
>> journal_checksum Enable checksumming of the journal transactions.
>> This will allow the recovery code in e2fsck and the
>> kernel to detect corruption in the kernel. It is a
>> @@ -206,6 +208,10 @@ nobh (a) cache disk block mapping information
>> "nobh" option tries to avoid associating buffer
>> heads (supported only for "writeback" mode).
>>
>> +mballoc (*) Use the mutliblock allocator for block allocation
speeeeling on "mutliblock" too :)
-Eric
-
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