linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: linux-ext4@vger.kernel.org
Cc: Ted Tso <tytso@mit.edu>
Subject: Journal async commit broken for data=ordered?
Date: Tue, 14 Feb 2012 16:55:36 +0100	[thread overview]
Message-ID: <20120214155536.GA16561@quack.suse.cz> (raw)

  Hello,

  I've just realized that JBD2_FEATURE_INCOMPAT_ASYNC_COMMIT breaks
guarantees of data=ordered mode in ext4. The problem is that async commit
code assumes that when a checksum of a transaction in the journal matches,
all necessary data is on disk. This is true for metadata but need not be so
for data - the whole transaction may be correctly on pernament storage
while some data is still sitting in drive's caches. Thus if a power failure
happens at that moment, we have broken guarantees of data=ordered mode.
Seeing that async commit code isn't used by default anyway (I remember
there used to be some problems with it), shouldn't we just rip it out?

								Honza

             reply	other threads:[~2012-02-14 15:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-14 15:55 Jan Kara [this message]
2012-02-14 20:56 ` Journal async commit broken for data=ordered? Andreas Dilger
2012-02-15 15:57   ` 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=20120214155536.GA16561@quack.suse.cz \
    --to=jack@suse.cz \
    --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).