From: Christoph Hellwig <hch@infradead.org>
To: viro@zeniv.linux.org.uk
Cc: jeffm@suse.com, chris.mason@oracle.com, jack@suse.cz,
reiserfs-devel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: [PATCH 2/2] reiserfs: make reiserfs default to barrier=flush
Date: Mon, 11 Jul 2011 14:26:19 -0400 [thread overview]
Message-ID: <20110711182619.GC12099@infradead.org> (raw)
In-Reply-To: <20110711182532.GA12099@infradead.org>
From: Jeff Mahoney <jeffm@suse.com>
Change the default reiserfs mount option to barrier=flush.
Signed-off-by: Jeff Mahoney <jeffm@suse.com>
Index: linux-2.6/fs/reiserfs/super.c
===================================================================
--- linux-2.6.orig/fs/reiserfs/super.c 2011-07-02 13:57:08.061117424 +0200
+++ linux-2.6/fs/reiserfs/super.c 2011-07-02 13:59:26.197782375 +0200
@@ -1643,6 +1643,7 @@ static int reiserfs_fill_super(struct su
/* Set default values for options: non-aggressive tails, RO on errors */
REISERFS_SB(s)->s_mount_opt |= (1 << REISERFS_SMALLTAIL);
REISERFS_SB(s)->s_mount_opt |= (1 << REISERFS_ERROR_RO);
+ REISERFS_SB(s)->s_mount_opt |= (1 << REISERFS_BARRIER_FLUSH);
/* no preallocation minimum, be smart in
reiserfs_file_write instead */
REISERFS_SB(s)->s_alloc_options.preallocmin = 0;
next prev parent reply other threads:[~2011-07-11 18:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 18:25 [PATCH 0/2] always default to issue cache flushes Christoph Hellwig
2011-07-11 18:25 ` [PATCH 1/2] ext3: make ext3 mount default to barrier=1 Christoph Hellwig
2011-07-11 19:17 ` Jan Kara
2011-07-11 19:20 ` Christoph Hellwig
2011-07-11 22:23 ` Ted Ts'o
2011-07-12 0:16 ` Eric Sandeen
2011-07-12 13:24 ` Chris Mason
2011-07-14 15:19 ` Christoph Hellwig
2011-07-11 18:26 ` Christoph Hellwig [this message]
2011-07-11 19:19 ` [PATCH 0/2] always default to issue cache flushes Jan Kara
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=20110711182619.GC12099@infradead.org \
--to=hch@infradead.org \
--cc=chris.mason@oracle.com \
--cc=jack@suse.cz \
--cc=jeffm@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).