[Pacemaker] lvm resource doesn't start

[David Coulson]

If clvmd hangs, you probably don't have fencing configured properly - It will block IO until a node is fenced correctly.




On May 12, 2012, at 12:16 PM, Frank Van Damme wrote:

> Hi list,
> 
> I'm assembling a cluster for A/P nfs on Debian Squeeze (6.0). For
> flexibility I want with LVM. So the goal is to have the cluster start
> the volume group (ocf::heartbeat::LVM), then mount the file system
> (ocf::heartbeat::Filesystem), add the cluster IP
> (ocf::heartbeat::IPaddr2), and start the (ocf::heartbeat::)nfsserver.
> 
> I've had trouble to start the volume group, however. When one node
> goes down, I can't start the volume group on the second. "crm resource
> start" returns nothing and the resource is simply still stopped.
> I suspect there is a problem with clvm, since the command "vgs" (on
> the one surviving node) hangs forever. I see errors in the system log
> "INFO: task clvmd:2568 blocked for more than 120 seconds."
> 
> The point of having a cluster is to still be able to access the vg
> after a node goes down, so. what am I ding (or thinking) wrong here?
> 
> -- 
> Frank Van Damme
> No part of this copyright message may be reproduced, read or seen,
> dead or alive or by any means, including but not limited to telepathy
> without the benevolence of the author.
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org