Tom Parker writes:
> On 09/17/2013 04:18 AM, Lars Marowsky-Bree wrote:
>
>> On 2013-09-16T16:36:38, Tom Parker wrote:
>>
>>> 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
On 09/17/2013 04:18 AM, Lars Marowsky-Bree wrote:
> On 2013-09-16T16:36:38, Tom Parker 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 corru
17.09.2013 20:51, Tom Parker wrote:
>
> On 09/17/2013 01:13 AM, Vladislav Bogdanov wrote:
>> 14.09.2013 07:28, Tom Parker wrote:
>>> Hello All
>>>
>>> Does anyone know of a good way to prevent pacemaker from declaring a vm
>>> dead if it's rebooted from inside the vm. It seems to be detecting the
On 09/17/2013 01:13 AM, Vladislav Bogdanov wrote:
> 14.09.2013 07:28, Tom Parker wrote:
>> Hello All
>>
>> Does anyone know of a good way to prevent pacemaker from declaring a vm
>> dead if it's rebooted from inside the vm. It seems to be detecting the
>> vm as stopped for the brief moment betwee
Lars Marowsky-Bree writes:
> On 2013-09-17T11:38:34, Ferenc Wagner wrote:
>
>> On the other hand, doesn't the recover action after a monitor failure
>> consist of a stop action on the original host before the new start, just
>> to make sure? Or maybe I'm confusing things...
>
> Yes, it would -
On 2013-09-17T11:38:34, Ferenc Wagner wrote:
> On the other hand, doesn't the recover action after a monitor failure
> consist of a stop action on the original host before the new start, just
> to make sure? Or maybe I'm confusing things...
Yes, it would - but it seems there's a brief period du
Lars Marowsky-Bree writes:
> 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
On 2013-09-16T16:36:38, Tom Parker 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 lockin
14.09.2013 07:28, Tom Parker wrote:
> Hello All
>
> Does anyone know of a good way to prevent pacemaker from declaring a vm
> dead if it's rebooted from inside the vm. It seems to be detecting the
> vm as stopped for the brief moment between shutting down and starting
> up. Often this causes the
On 09/14/2013 07:18 AM, Lars Marowsky-Bree wrote:
> On 2013-09-14T00:28:30, Tom Parker wrote:
>
>> Does anyone know of a good way to prevent pacemaker from declaring a vm
>> dead if it's rebooted from inside the vm. It seems to be detecting the
>> vm as stopped for the brief moment between shutt
On 2013-09-14T00:28:30, Tom Parker wrote:
> Does anyone know of a good way to prevent pacemaker from declaring a vm
> dead if it's rebooted from inside the vm. It seems to be detecting the
> vm as stopped for the brief moment between shutting down and starting
> up.
Hrm. Good question. Because
Hello All
Does anyone know of a good way to prevent pacemaker from declaring a vm
dead if it's rebooted from inside the vm. It seems to be detecting the
vm as stopped for the brief moment between shutting down and starting
up. Often this causes the cluster to have two copies of the same vm if
th
12 matches
Mail list logo
