Re: [Pacemaker] How to prevent locked I/O using Pacemaker with Primary/Primary DRBD/OCFS2 (Ubuntu 10.10)

2011-04-07 Thread Mike Reid
two-node cluster (OCFS2)? Message: 1 Date: Thu, 7 Apr 2011 02:50:09 +0200 From: Lars Ellenberg lars.ellenb...@linbit.com To: pacemaker@oss.clusterlabs.org Subject: Re: [Pacemaker] How to prevent locked I/O using Pacemaker with Primary/Primary DRBD/OCFS2 (Ubuntu 10.10) Message-ID

Re: [Pacemaker] How to prevent locked I/O using Pacemaker with Primary/Primary DRBD/OCFS2 (Ubuntu 10.10)

2011-04-06 Thread Reid, Mike
Lars, Thank you for your comments. I did confirm I was running 8.3.8.1, and I have even upgraded to 8.3.10 but am still experiencing the same I/O lock issue. I definitely agree with you, DRBD is behaving exactly as instructed, being properly fenced, etc. I am quite new to DRBD (and OCFS2),

Re: [Pacemaker] How to prevent locked I/O using Pacemaker with Primary/Primary DRBD/OCFS2 (Ubuntu 10.10)

2011-04-06 Thread Lars Ellenberg
On Tue, Apr 05, 2011 at 01:59:00PM -0400, Jean-Francois Malouin wrote: Hi, I don't want to hijack this thread so feel free to change the Subject line if you feel like it. * Lars Ellenberg lars.ellenb...@linbit.com [20110404 16:56]: On Mon, Apr 04, 2011 at 01:34:48PM -0600, Mike Reid

Re: [Pacemaker] How to prevent locked I/O using Pacemaker with Primary/Primary DRBD/OCFS2 (Ubuntu 10.10)

2011-04-06 Thread Lars Ellenberg
On Wed, Apr 06, 2011 at 10:26:24AM -0600, Reid, Mike wrote: Lars, Thank you for your comments. I did confirm I was running 8.3.8.1, and I have even upgraded to 8.3.10 but am still experiencing the same I/O lock issue. I definitely agree with you, DRBD is behaving exactly as instructed,

Re: [Pacemaker] How to prevent locked I/O using Pacemaker with Primary/Primary DRBD/OCFS2 (Ubuntu 10.10)

2011-04-05 Thread Raoul Bhatia [IPAX]
On 04/04/11 22:55, Lars Ellenberg wrote: * resource minor=0 cs=WFConnection ro1=Primary ro2=Unknownds1=UpToDate ds2=Outdated / Why keep people using this pseudo xml output? where does that come from? we should un-document this. This is to be consumed by other programs (like the LINBIT

Re: [Pacemaker] How to prevent locked I/O using Pacemaker with Primary/Primary DRBD/OCFS2 (Ubuntu 10.10)

2011-04-05 Thread Jean-Francois Malouin
Hi, I don't want to hijack this thread so feel free to change the Subject line if you feel like it. * Lars Ellenberg lars.ellenb...@linbit.com [20110404 16:56]: On Mon, Apr 04, 2011 at 01:34:48PM -0600, Mike Reid wrote: All, I am running a two-node web cluster on OCFS2 (v1.5.0) via DRBD

[Pacemaker] How to prevent locked I/O using Pacemaker with Primary/Primary DRBD/OCFS2 (Ubuntu 10.10)

2011-04-04 Thread Mike Reid
All, I am running a two-node web cluster on OCFS2 (v1.5.0) via DRBD Primary/Primary (v8.3.8) and Pacemaker. Everything seems to be working great, except during testing of hard-boot scenarios. Whenever I hard-boot one of the nodes, the other node is successfully fenced and marked ³Outdated² *

Re: [Pacemaker] How to prevent locked I/O using Pacemaker with Primary/Primary DRBD/OCFS2 (Ubuntu 10.10)

2011-04-04 Thread Lars Ellenberg
On Mon, Apr 04, 2011 at 01:34:48PM -0600, Mike Reid wrote: All, I am running a two-node web cluster on OCFS2 (v1.5.0) via DRBD Primary/Primary (v8.3.8) and Pacemaker. Everything seems to be working If you want to stay with 8.3.8, make sure you are using 8.3.8.1 (note the trailing .1), or

Re: [Pacemaker] How to prevent locked I/O using Pacemaker with Primary/Primary DRBD/OCFS2 (Ubuntu 10.10)

2011-04-04 Thread Devin Reade
I ran into a similar behavior with an earlier version of glusterfs on raw disk (not DRBD). In that case it was a bug in gluster that, although the nodes were supposed to be operating in a mirror configuration, the one remaining node would refuse to service requests after the other node was