On 2013-09-16T16:36:38, Tom Parker <[email protected]> wrote:
> > Can you kindly file a bug report here so it doesn't get lost
> > https://github.com/ClusterLabs/resource-agents/issues ?
> Submitted (Issue *#308)*
Thanks.
> It definitely leads to data corruption and I think has to do with the
> way that the locking is not working properly on my lvm partitions.
Well, not really an LVM issue. The RA thinks the guest is gone, the
cluster reacts and schedules it to be started (perhaps elsewhere); and
then the hypervisor starts it locally again *too*.
I think changing those libvirt settings to "destroy" could work - the
cluster will then restart the guest appropriately, not the hypervisor.
Regards,
Lars
--
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
