If you are using clvm, you shouldn't wory about volume_list because clvm allows nodes to activate LVs in all nodes.
Please check what is "locking_type" in lvm.conf . It should be 3 in RHEL5 so that when clvm starts it can enable all clustered VGs.
If the issue still persists, please chkconfig all cluster services off and reboot nodes. Once nodes are up start the cluster services in order. Please note that cluster should be quorate for clvm to start fine.
On Fri, Aug 27, 2010 at 11:36 PM, Michael Smith <msmith@cbnco.com> wrote:
Hi,
When a CLVM cluster comes up, the LVs in the clustered volume groups are "not available". I can use the heartbeat LVM resource to trigger a "vgchange -aly", but I'm wondering if there's a way to configure it to happen automatically. It'd make my cluster config simpler.
I'm not positive, but I guess the volume_list directive in lvm.conf might be able to do it. Is there a way to tell it to activate all LVs on all VGs, or do I have to list the VGs by name?
Thanks,
Mike
_______________________________________________
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/
_______________________________________________ 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/
