Experts, I am trying to use Linux heartbeat (2.1.4 with v1 style resource configuration) with LVM to mount Lustre MDTs. My configuration is simple, ha.cf and haresources file is attached. I have an interesting observation. When I reboot MDS nodes and start MDTs with "service heartbeat start" simultaneously on both mds nodes, sometimes I get following message:
mds1: 2009/12/10_13:48:08 CRITICAL: Resource LVM::mgsvg is active, and should not be! mds1: 2009/12/10_13:48:08 CRITICAL: Non-idle resources can affect data integrity! mds2: 2009/12/10_13:47:08 CRITICAL: Resource LVM::mgsvg is active, and should not be! mds2: 2009/12/10_13:47:08 CRITICAL: Non-idle resources can affect data integrity! and heartbeat on both mds nodes does not start any resource (even after waiting for 35 minutes). Has anyone seen this before? /etc/ha.d/ha.cf : ============ use_logd on logfile /var/log/ha-log debugfile /var/log/ha-debug logfacility local0 keepalive 2 deadtime 120 warntime 10 initdead 120 udpport 694 mcast eth0 239.0.0.3 694 1 0 mcast ib0 224.0.0.3 694 1 0 node mds1 node mds2 auto_failback off stonith_host mds1 external/ipmi mds2 mds2-sp root changeme lanplus stonith_host mds2 external/ipmi mds1 mds1-sp root changeme lanplus /etc/ha.d/haresources : ================= mds1 LVM::mgsvg Filesystem::/dev/mgsvg/mgs::/lustre/mgs::lustre mds1 LVM::home1vg Filesystem::/dev/home1vg/home1::/lustre/home1::lustre mds1 LVM::data1vg Filesystem::/dev/data1vg/data1::/lustre/data1::lustre mds2 LVM::flushvg Filesystem::/dev/flushvg/flush::/lustre/flush::lustre mds2 LVM::data2vg Filesystem::/dev/data2vg/data2::/lustre/data2::lustre mds2 LVM::home2vg Filesystem::/dev/home2vg/home2::/lustre/home2::lustre Cheers, _Atul _______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
