I haven't tried it in a cluster yet. I was planning on using HP's
MC-ServiceGuard to deal with HA clustering. I don't see why the LUNs that
are used on one system with mdadm can't be used another, since the RAID
block is on the disk and is readable even on a system upon which it wasn't
created on. /etc/mdadm.conf will ofcourse need to be copied and kept
current on all cluster nodes, but with the config file and the RAID block
on the disk, an "mdadm --assemble" should work. Importing the LVM
structures should then also not be a problem.
Assuming that the underlying devices are "clean" this may indeed
work... Sometimes.
However, things like the dirty region log are going to be a mess.
Imagine that you've got apache running on node 1 using one GFS volume,
and mysql on the second using another - both backed onto the same md
physical volume. They will each be writing to the same DRL their
dirty regions, and trampling all over each other's status information.
Then node2 crashes with some IO in progress. In the time taken for it
to reboot, the DRL could have been totally over-written by node1 - at
this point there may be differences between the two underlying devices
that you don't know about, and you've just caused data corruption.
Even if the devices were clean when the second node came up, the first
has it open, and the fact that it's not in a clean/shutdown state is
likely to be recorded too, and node2 is going to be unhappy about that
too.
All in all, unless md is cluster "aware", it's likely to cause you
trouble down the line....
Graham
_______________________________________________
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/
