Linux RAID subsystem development
 help / color / mirror / Atom feed
* Suspected corruption on ACID databases due to no barrier support in ext3 on software raid-5 and hard resets
@ 2008-06-28  8:53 Leon Woestenberg
  2008-06-28 12:40 ` Jon Nelson
  0 siblings, 1 reply; 3+ messages in thread
From: Leon Woestenberg @ 2008-06-28  8:53 UTC (permalink / raw)
  To: LinuxRaid, sandeen

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2008-06-29 19:44 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox