-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stuart D. Gathman wrote: > If out of order writes are enabled, then your server should hold power > to the disk drives for part of a second after disabling further writes > in software. LVM is a low risk because LVM changes are comparatively > rare, and the modification window is small. But, theoretically, if > you lost power right at the instant you pressed return on lvcreate, > lvextend, or lvremove, on a system with busy disk io, you could corrupt > the LVM metadata. LVM metadata I/O does not pass through device-mapper unless you are stacking volume groups so I'm not sure how your comment regarding barriers is relevant here. It's also only going to affect devices under snapshot and multipath mappings. How does this differ from updating an MSDOS or GPT partition table, for example? Kind regards, Bryn. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFGSB/v6YSQoMYUY94RAubIAJ4vcB/tqherGhmW/M6n1wcO5KGungCffw1w ISfLoRVk6CP3EryIzHTolXA= =g18w -----END PGP SIGNATURE----- _______________________________________________ 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/
