Marco Marino <[email protected]> writes: > Ferenc, regarding the flag use_lvmetad in > /usr/lib/ocf/resource.d/heartbeat/LVM I read: > >> lvmetad is a daemon that caches lvm metadata to improve the >> performance of LVM commands. This daemon should never be used when >> volume groups exist that are being managed by the cluster. The >> lvmetad daemon introduces a response lag, where certain LVM commands >> look like they have completed (like vg activation) when in fact the >> command is still in progress by the lvmetad. This can cause >> reliability issues when managing volume groups in the cluster. For >> Example, if you have a volume group that is a dependency for another >> application, it is possible the cluster will think the volume group >> is activated and attempt to start the application before volume group >> is really accesible... lvmetad is bad. > > in the function LVM_validate_all()
Wow, if this is true, then this is serious breakage in LVM. Thanks for the pointer. I think this should be brought up with the LVM developers. -- Feri _______________________________________________ Users mailing list: [email protected] http://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
