[DRBD-user] RedHat Clustering Services does not fence when DRBD breaks

Andrew Gideon ag928272 at gideon.org
Wed Dec 1 19:22:52 CET 2010

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.

On Tue, 23 Nov 2010 11:04:38 -0800, Joe Hammerman wrote:

On Wed, 01 Dec 2010 17:38:05 +0100, Florian Haas wrote:

> - DRBD detects peer is gone
> - DRBD freezes I/O
> - DRBD fires the fence-peer handler and observes its exit code as per
> the convention explained in
> http://www.drbd.org/users-guide/s-fence-peer.html - if all is well (peer
> is definitely no longer accessing the disk), DRBD un-freezes I/O and
> resumes normal operations.

I'm doing something similar: adopting a xen/kvm fence we use for Cluster 
Suite to DRBD.  

I noticed that, if the fence handler returns 6 (peer refused to be 
outdated), the connection is of a state:

 1: cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown C s----
    ns:0 nr:0 dw:4096 dr:28 al:1 bm:3 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0

Is this still frozen?  How does one know?  

Where can I find documentation for the string "s----" ?  I'm missing it 
if it is in http://www.drbd.org/users-guide/ch-admin.html#s-proc-drbd


	- Andrew

More information about the drbd-user mailing list