Re: [Linux-HA] Forcing primitive_nfslock away from node

2011-09-18 Thread Andrew Beekhof
On Mon, Sep 19, 2011 at 1:19 PM, Dimitri Maziuk wrote: > On 9/18/2011 7:22 PM, Andrew Beekhof wrote: >> On Fri, Aug 19, 2011 at 7:31 AM, Dimitri Maziuk   >> wrote: > ... >> No it means one of more filesystem_drbd and primitive_nfslock >> operations failed really badly on node1. >> Possibly it was

Re: [Linux-HA] Forcing primitive_nfslock away from node

2011-09-18 Thread Dimitri Maziuk
On 9/18/2011 7:22 PM, Andrew Beekhof wrote: > On Fri, Aug 19, 2011 at 7:31 AM, Dimitri Maziuk wrote: ... > No it means one of more filesystem_drbd and primitive_nfslock > operations failed really badly on node1. > Possibly it was the initial health check (to check it wasn't already > running befor

Re: [Linux-HA] Forcing primitive_nfslock away from node

2011-09-18 Thread Andrew Beekhof
On Fri, Aug 19, 2011 at 7:31 AM, Dimitri Maziuk wrote: > > WTH does this mean (from node2): > > pengine: [16069]: notice: clone_print:  Master/Slave Set: master_drbd > pengine: [16069]: notice: short_print:      Masters: [ node1 ] > pengine: [16069]: notice: short_print:      Slaves: [ node2 ] > p

[Linux-HA] Forcing primitive_nfslock away from node

2011-08-18 Thread Dimitri Maziuk
WTH does this mean (from node2): pengine: [16069]: notice: clone_print: Master/Slave Set: master_drbd pengine: [16069]: notice: short_print: Masters: [ node1 ] pengine: [16069]: notice: short_print: Slaves: [ node2 ] pengine: [16069]: notice: native_print: filesystem_drbd#011(ocf::hear