On 10/4/2010 7:55 PM, Jay wrote: > the other disk and lvcovert. But it wouldn't work, saying I needed to > add space on yet a third device for the log. Either that, or I could > keep the mirror log in memory. Lvm would have to rebuild a 1TB mirror > every time the system was rebooted if the log was left in memory. That > doesn't sound efficient. So. Put the log on disk. I couldn't find > an answer in man pages, but if the log is lost, then is the whole mirror > lost ? That would mean to have the benefits of a mirror, the log would > have to be at least as reliable as the mirror itself (or > inconsequential). > > So, another mirror would have to be built of tiny size to hold the log, > then lvconvert can be given something like -log disk /dev/vghuh/lvtiny, > etc.. As you have noticed, LVM mirror support is basically broken or not fully implemented yet. The mirror log SHOULD be stored on both legs of the mirror in a block allocated automatically in the metadata area by lvm, but isn't. If you want to mirror, you should do so using mdadm and then use the md device as an lvm pv. _______________________________________________ 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/
