From: Asdo <asdo@shiftmail.org>
To: Jan Kara <jack@suse.cz>, linux-ext4@vger.kernel.org
Subject: Re: ext4 barrier on SCSI vs SATA?
Date: Mon, 14 May 2012 12:33:03 +0200 [thread overview]
Message-ID: <4FB0DF5F.2060400@shiftmail.org> (raw)
In-Reply-To: <20120514090230.GA5353@quack.suse.cz>
On 05/14/12 11:02, Jan Kara wrote:
>> 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.
> This is not true. Both cache flushes and barriers were implemented by
> the same mechanism in older kernels. Thus if the device did not properly
> propagate the barrier capability, then fsync did not provide any guarantees
> in case of power failure (if there are volalile write caches in the storage
> device).
Oh! Thanks I had not realized this.
So, if barrier IS provided by the underlying blockdevice but filesystem
is nevertheless mounted as nobarrier (as an explicit option) would
database flushes (fsync) for files on THAT filesystem work properly or not?
Thanks for your insight
next prev parent reply other threads:[~2012-05-14 10:33 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
2012-05-14 9:02 ` Jan Kara
2012-05-14 10:33 ` Asdo [this message]
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=4FB0DF5F.2060400@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).