From: Eric Sandeen <sandeen@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: barriers off by default?
Date: Thu, 15 May 2008 19:58:15 -0500 [thread overview]
Message-ID: <482CDC27.4090505@redhat.com> (raw)
In-Reply-To: <20080516002145.GA24369@duck.suse.cz>
Jan Kara wrote:
> On Thu 15-05-08 15:44:04, Eric Sandeen wrote:
>> + if (!test_opt(sb, BARRIER)) {
>> + seq_puts(seq, ",barrier=0");
>> + } else {
>> + /*
>> + * jbd inherits the barrier flag from ext3, and jbd may actually
>> + * turn off barriers if a write fails, so it's the real test.
>> + */
>> + if (journal && !(journal->j_flags & JFS_BARRIER))
>> + seq_puts(seq, ",barrier=1(failed)");
>> + }
Actually, since /proc/mounts should substitute for mtab I should not be
putting chatty informational messages in there, should I!
/*
* jbd inherits the barrier flag from ext3, and jbd may actually
* turn off barriers if a write fails, so it's the real test.
*/
if (!test_opt(sb, BARRIER) ||
(journal && !(journal->j_flags & JFS_BARRIER)))
seq_puts(seq, ",barrier=0");
is a better plan.
-Eric
next prev parent reply other threads:[~2008-05-16 0:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 15:56 barriers off by default? Eric Sandeen
2008-05-12 17:30 ` Eric A
2008-05-12 17:53 ` Eric Sandeen
[not found] ` <72c5d9a0805121150j58482bc6qd57a87089ce4414e@mail.gmail.com>
2008-05-12 18:51 ` Fwd: " Eric A
2008-05-12 19:00 ` Eric Sandeen
2008-05-12 19:11 ` Eric A
2008-05-12 19:15 ` Eric Sandeen
2008-05-15 14:43 ` Jan Kara
2008-05-15 16:00 ` Eric Sandeen
2008-05-15 16:21 ` Andreas Dilger
2008-05-15 18:34 ` Eric Sandeen
2008-05-15 20:44 ` Eric Sandeen
2008-05-16 0:21 ` Jan Kara
2008-05-16 0:58 ` Eric Sandeen [this message]
2008-05-17 17:38 ` Theodore Tso
2008-05-17 19:02 ` 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=482CDC27.4090505@redhat.com \
--to=sandeen@redhat.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.