mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Harald Arnesen <skogtun.harald@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu
Subject: [ext4] Documentation patch
Date: Mon, 01 Dec 2008 17:46:56 +0100	[thread overview]
Message-ID: <8763m3u9kv.fsf@basilikum.skogtun.org> (raw)

My first patch, hope it goes through ok! 
Applies to 2.6.28-rc6-00184-gd9d060a.

Compare ext4's journalling with anything but ext3's. These use the same
journalling modes, most other Linux filesystems do only metadata
journalling.

Signed-off-by: Harald Arnesen <harald@skogtun.org>

========================================================================
diff --git a/Documentation/filesystems/ext4.txt b/Documentation/filesystems/ext4.txt
index 174eaff..5bbe79e 100644
--- a/Documentation/filesystems/ext4.txt
+++ b/Documentation/filesystems/ext4.txt
@@ -61,7 +61,7 @@ Note: More extensive information for getting started with ext4 can be
   - When comparing performance with other filesystems, remember that
     ext3/4 by default offers higher data integrity guarantees than most.
     So when comparing with a metadata-only journalling filesystem, such
-    as ext3, use `mount -o data=writeback'.  And you might as well use
+    as jfs or xfs, use `mount -o data=writeback'.  And you might as well use
     `mount -o nobh' too along with it.  Making the journal larger than
     the mke2fs default often helps performance with metadata-intensive
     workloads.
-- 
Hilsen Harald.

             reply	other threads:[~2008-12-01 16:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-01 16:46 Harald Arnesen [this message]
2008-12-01 16:57 ` Christoph Hellwig
2008-12-01 17:58   ` Eric Sandeen
2008-12-01 20:58     ` Theodore Tso
2008-12-06 22:25       ` Theodore Tso
2008-12-06 23:33         ` Eric Sandeen
2008-12-07 18:39           ` Theodore Tso
2008-12-07 20:43             ` Eric Sandeen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8763m3u9kv.fsf@basilikum.skogtun.org \
    --to=skogtun.harald@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome