All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Sahitya Tummala <stummala@codeaurora.org>,
	Andreas Dilger <adilger.kernel@dilger.ca>,
	linux-ext4@vger.kernel.org
Subject: Re: fsync_mode mount option for ext4
Date: Tue, 28 May 2019 23:56:47 -0700	[thread overview]
Message-ID: <20190529065647.GA8405@infradead.org> (raw)
In-Reply-To: <20190529052332.GB6210@mit.edu>

On Wed, May 29, 2019 at 01:23:32AM -0400, Theodore Ts'o wrote:
> If you have protection against sudden shutdown, then nobarrier is
> perfectly safe --- which is to say, if it is guaranteed that any
> writes sent to device will be persisted after a crash, then nobarrier
> is perfectly safe.  So for example, if you are using ext4 connected to
> a million dollar EMC Storage Array, which has battery backup, using
> nobarrier is perfectly safe.

And while we had a few oddities in the past in general any such device
will obviously not claim to even have a volatile write cache, so
nobarrier or this broken proposed mount option won't actually make any
difference.

  reply	other threads:[~2019-05-29  6:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-28  3:22 fsync_mode mount option for ext4 Sahitya Tummala
2019-05-28  3:40 ` Theodore Ts'o
2019-05-28  3:48   ` Sahitya Tummala
2019-05-28 13:13     ` Theodore Ts'o
2019-05-29  4:07       ` Sahitya Tummala
2019-05-29  5:23         ` Theodore Ts'o
2019-05-29  6:56           ` Christoph Hellwig [this message]
2019-05-29 10:48           ` Sahitya Tummala
2019-05-29 15:13             ` 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=20190529065647.GA8405@infradead.org \
    --to=hch@infradead.org \
    --cc=adilger.kernel@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=stummala@codeaurora.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 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.