From: Asdo <asdo@shiftmail.org>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext4 barrier on SCSI vs SATA?
Date: Fri, 11 May 2012 07:08:20 +0200 [thread overview]
Message-ID: <4FAC9EC4.1000906@shiftmail.org> (raw)
In-Reply-To: <20120509195056.GH5092@quack.suse.cz>
On 05/09/12 21:50, Jan Kara wrote:
> []
I have some troubles understanding the barriers thing, can you help me?
In the past some blockdevices would not provide / propagate the
barriers, e.g. MD raid 5 would not. So filesystems during mount would
try the barrier operation and see that it wouldn't work, so they would
disable barrier option and mount as nobarrier.
However the flush was always available (I think), in fact databases
would not corrupt (not even above ext4 nobarrier, above a raid5 without
barriers) if fsync was called at proper times.
So first question is : why filesystems were not using the flush as a
barrier like databases did?
Second question is : was a nobarrier mount (ext4) more risky in terms of
data or metadata lost on sudden power loss?
Thank you
Asdo
next prev parent reply other threads:[~2012-05-11 7:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 10:35 ext4 barrier on SCSI vs SATA? Daniel Pocock
2012-05-09 19:50 ` Jan Kara
2012-05-11 5:08 ` Asdo [this message]
2012-05-14 9:02 ` Jan Kara
2012-05-14 10:33 ` Asdo
2012-05-14 10:51 ` 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=4FAC9EC4.1000906@shiftmail.org \
--to=asdo@shiftmail.org \
--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 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).