From patchwork Fri Oct 17 11:11:57 2008 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Theodore Ts'o X-Patchwork-Id: 4828 Return-Path: X-Original-To: patchwork-incoming@ozlabs.org Delivered-To: patchwork-incoming@ozlabs.org Received: from vger.kernel.org (vger.kernel.org [209.132.176.167]) by ozlabs.org (Postfix) with ESMTP id 979E5DDF9C for ; Fri, 17 Oct 2008 22:12:01 +1100 (EST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752506AbYJQLMA (ORCPT ); Fri, 17 Oct 2008 07:12:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752569AbYJQLMA (ORCPT ); Fri, 17 Oct 2008 07:12:00 -0400 Received: from www.church-of-our-saviour.org ([69.25.196.31]:54540 "EHLO thunker.thunk.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752506AbYJQLL7 (ORCPT ); Fri, 17 Oct 2008 07:11:59 -0400 Received: from root (helo=closure.thunk.org) by thunker.thunk.org with local-esmtp (Exim 4.50 #1 (Debian)) id 1KqnFO-0001vg-1M; Fri, 17 Oct 2008 07:11:58 -0400 Received: from tytso by closure.thunk.org with local (Exim 4.69) (envelope-from ) id 1KqnFN-0005kN-Ej; Fri, 17 Oct 2008 07:11:57 -0400 Date: Fri, 17 Oct 2008 07:11:57 -0400 From: Theodore Tso To: dcg Cc: linux-ext4@vger.kernel.org Subject: Re: [PATCH] Update Documentation/filesystems/ext4.txt Message-ID: <20081017111157.GA21503@mit.edu> References: <20081017011008.6c3b12ef@diego-desktop> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20081017011008.6c3b12ef@diego-desktop> User-Agent: Mutt/1.5.17+20080114 (2008-01-14) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: tytso@mit.edu X-SA-Exim-Scanned: No (on thunker.thunk.org); SAEximRunCond expanded to false Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On Fri, Oct 17, 2008 at 01:10:08AM +0200, dcg wrote: > Since Ext4 is supposed to be stable in 2.6.28-rc, Documentation should be > updated...it needs more updates, of course, I don't really know what > parts should really be updated Thanks, here's the revised version of the patch which I have in the ext4 patch queue. > PD: the wiki needs some update aswell. I'll update the wiki after 2.6.28-rc1 and the merge window closes. - Ted ext4: Update Documentation/filesystems/ext4.txt From: dcg Since Ext4 is supposed to be stable in 2.6.28-rc, ext4's documentation file should be updated. [ More updates also added by Theodore Ts'o. ] Signed-off-by: Diego Calleja Signed-off-by: "Theodore Ts'o" --- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Index: 2.6/Documentation/filesystems/ext4.txt =================================================================== diff --git a/Documentation/filesystems/ext4.txt b/Documentation/filesystems/ext4.txt index eb154ef..7fd9b9b 100644 --- a/Documentation/filesystems/ext4.txt +++ b/Documentation/filesystems/ext4.txt @@ -2,10 +2,10 @@ Ext4 Filesystem =============== -This is a development version of the ext4 filesystem, an advanced level -of the ext3 filesystem which incorporates scalability and reliability -enhancements for supporting large filesystems (64 bit) in keeping with -increasing disk capacities and state-of-the-art feature requirements. +Ext4 is an an advanced level of the ext3 filesystem which incorporates +scalability and reliability enhancements for supporting large filesystems +(64 bit) in keeping with increasing disk capacities and state-of-the-art +feature requirements. Mailing list: linux-ext4@vger.kernel.org @@ -14,7 +14,7 @@ Mailing list: linux-ext4@vger.kernel.org =========================== - Compile and install the latest version of e2fsprogs (as of this - writing version 1.41) from: + writing version 1.41.3) from: http://sourceforge.net/project/showfiles.php?group_id=2406 @@ -36,11 +36,9 @@ Mailing list: linux-ext4@vger.kernel.org # mke2fs -t ext4 /dev/hda1 - Or configure an existing ext3 filesystem to support extents and set - the test_fs flag to indicate that it's ok for an in-development - filesystem to touch this filesystem: + Or to configure an existing ext3 filesystem to support extents: - # tune2fs -O extents -E test_fs /dev/hda1 + # tune2fs -O extents /dev/hda1 If the filesystem was created with 128 byte inodes, it can be converted to use 256 byte for greater efficiency via: @@ -104,8 +102,8 @@ exist yet so I'm not sure they're in the near-term roadmap. The big performance win will come with mballoc, delalloc and flex_bg grouping of bitmaps and inode tables. Some test results available here: - - http://www.bullopensource.org/ext4/20080530/ffsb-write-2.6.26-rc2.html - - http://www.bullopensource.org/ext4/20080530/ffsb-readwrite-2.6.26-rc2.html + - http://www.bullopensource.org/ext4/20080818-ffsb/ffsb-write-2.6.27-rc1.html + - http://www.bullopensource.org/ext4/20080818-ffsb/ffsb-readwrite-2.6.27-rc1.html 3. Options ========== @@ -253,8 +251,6 @@ nobh (a) cache disk block mapping information "nobh" option tries to avoid associating buffer heads (supported only for "writeback" mode). -mballoc (*) Use the multiple block allocator for block allocation -nomballoc disabled multiple block allocator for block allocation. stripe=n Number of filesystem blocks that mballoc will try to use for allocation size and alignment. For RAID5/6 systems this should be the number of data