Linux RAID subsystem development
 help / color / mirror / Atom feed
From: "Leon Woestenberg" <leon.woestenberg@gmail.com>
To: Jon Nelson <jnelson-linux-raid@jamponi.net>
Cc: LinuxRaid <linux-raid@vger.kernel.org>, sandeen@sandeen.net
Subject: Re: Suspected corruption on ACID databases due to no barrier support in ext3 on software raid-5 and hard resets
Date: Sun, 29 Jun 2008 21:44:26 +0200	[thread overview]
Message-ID: <c384c5ea0806291244n4721d97et37f16286af80f368@mail.gmail.com> (raw)
In-Reply-To: <cccedfc60806280540j4ff2635cu494eaeb685459e6@mail.gmail.com>

Hello Jon,

On Sat, Jun 28, 2008 at 2:40 PM, Jon Nelson
<jnelson-linux-raid@jamponi.net> wrote:
> database, the data is not being written to new files but existing
> files are being modified. If it were new files, then data=ordered
> would be fine but since it is existing files being modified (in-place)
> data=journal is more appropriate.
>
data=ordered should be fine in any case. Data is written directly to
disk (either modified data or newly allocated data, this does not
matter) and meta data goes through the journal log, written after the
data.

The problem lies in the fact that the driver can re-order the writes,
if write caching is enabled and barriers are not used (as in my case,
as md raid 5 does not support barriers).

> Of course, I might be wrong and would appreciate (polite) correction
> but this is what I've been led to believe.
>
I hope I was polite enough.

> Now, due to the hardware reset, write caching on drives is a problem.
>
Only because they re-order, not because of anything else.

> That you may have to disable - I've not found substantial performance
> differences on when write caching is enabled anyway, but surely that
> depends on a great many factors.
>
Indeed, we will be doing tests with that.

Regards,
-- 
Leon

      reply	other threads:[~2008-06-29 19:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-28  8:53 Suspected corruption on ACID databases due to no barrier support in ext3 on software raid-5 and hard resets Leon Woestenberg
2008-06-28 12:40 ` Jon Nelson
2008-06-29 19:44   ` Leon Woestenberg [this message]

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=c384c5ea0806291244n4721d97et37f16286af80f368@mail.gmail.com \
    --to=leon.woestenberg@gmail.com \
    --cc=jnelson-linux-raid@jamponi.net \
    --cc=linux-raid@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    /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