From: "Leon Woestenberg" <leon.woestenberg@gmail.com>
To: LinuxRaid <linux-raid@vger.kernel.org>, sandeen@sandeen.net
Subject: Suspected corruption on ACID databases due to no barrier support in ext3 on software raid-5 and hard resets
Date: Sat, 28 Jun 2008 10:53:01 +0200 [thread overview]
Message-ID: <c384c5ea0806280153j426585f1q212c44f983a641e1@mail.gmail.com> (raw)
Hello all,
we are quite sure we are hitting data corruption on a few % of cases
on ACID* databases due to write caching enabled on drives in a
software RAID-5 configuration with ext3 in default data=ordered mode.
The machines are hard reset by a hardware watchdog when some esoteric
PCI device misbehaves.
We understand Linux software raid 5 does not pass-down barriers, is
that correct, and is this being implemented?
Also, our near-term direction of solution would be
0) disable write caches altogether, probably not feasible due to the
performance regression involved.
1) solve the misbehave (cause of reset).
2) use a shorter timed software watchdog to trigger the drives into
disabling their write caches, so that an imminent reboot has its
commits ordered.
Any other ideas?
Regards,
--
Leon
*http://en.wikipedia.org/wiki/ACID
next reply other threads:[~2008-06-28 8:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-28 8:53 Leon Woestenberg [this message]
2008-06-28 12:40 ` Suspected corruption on ACID databases due to no barrier support in ext3 on software raid-5 and hard resets Jon Nelson
2008-06-29 19:44 ` Leon Woestenberg
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=c384c5ea0806280153j426585f1q212c44f983a641e1@mail.gmail.com \
--to=leon.woestenberg@gmail.com \
--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