From: Eric Sandeen <sandeen@redhat.com>
To: Autif Khan <autif.mlist@gmail.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: How can I flush all writes before yanking the power cable?
Date: Thu, 07 Feb 2013 15:29:47 -0600 [thread overview]
Message-ID: <51141CCB.9060908@redhat.com> (raw)
In-Reply-To: <CADzUK1+_2FVpMfKBOBAL4Q0xYiPuOmXRBTfdO-=A=xMONOMeeQ@mail.gmail.com>
On 2/7/13 3:28 PM, Autif Khan wrote:
> On Thu, Feb 7, 2013 at 3:58 PM, Theodore Ts'o <tytso@mit.edu> wrote:
>> On Thu, Feb 07, 2013 at 02:37:02PM -0500, Autif Khan wrote:
>>>
>>> That was precisely my ignorance. I did not know about barrier. Adding
>>> it during mount ro and remount rw seems to have fixed these issues.
>>
>> You also didn't say what file system you were using. Was it ext4?
>> ext3? ext2? What kernel version? On modern kernels barrier is
>> enabled by default for both ext3 and ext4.
>
> The filesystem is ext4. Kernel version is 3.2.0
>
> I could not grep -i barrier in the kernel config. How is barrier
> enabled or disabled in the kernel by default?
in ext4_fill_super():
if ((def_mount_opts & EXT4_DEFM_NOBARRIER) == 0)
set_opt(sb, BARRIER);
It's a mount option, not a kernel config option.
-Eric
next prev parent reply other threads:[~2013-02-07 21:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 16:43 How can I flush all writes before yanking the power cable? Autif Khan
2013-02-07 18:12 ` Eric Sandeen
2013-02-07 19:37 ` Autif Khan
2013-02-07 20:58 ` Theodore Ts'o
2013-02-07 21:28 ` Autif Khan
2013-02-07 21:29 ` Eric Sandeen [this message]
2013-05-16 18:31 ` Autif Khan
2013-05-16 19:03 ` Theodore Ts'o
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=51141CCB.9060908@redhat.com \
--to=sandeen@redhat.com \
--cc=autif.mlist@gmail.com \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).