On Mon, 28 Mar 2011, Les Mikesell wrote:
On 3/26/2011 11:07 AM, Stuart D. Gathman wrote:
Is there some non-destructive diagnostic that can tell you if a running
machine can or can't manage write ordering correctly through all of its
software and hardware layers?
http://blog.nirkabel.org/2008/12/07/ext3-write-barriers-and-write-caching/
The above mentions a test program that demonstrates the ext3 weakness.
You should be able to run it in a test VM, and destroy (virtual power off)
the VM. When the barrier=1 mount option is turned on, the mapper is supposed
to log a warning if this is not supported at some level. There appear to
be disks, however, with hardware write caching that do not correct support
barriers. You must turn off hardware write caching on these models.
You can probably test the software stack by running md + lvm in a VM and
destroying the VM. To test the whole thing, you could run a test VM
on an external SATA/USB/Firewire drive and power off the drive during
the test. This *shouldn't* affect your production VMs (but I'd use separate
hardware just to be sure.)
What a headache. I want to be working on my programming projects, not
becoming a super admin.
--
Stuart D. Gathman <stuart@bmsi.com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
