I am trying to setup two systems with two replicated volumes in two cluster 
configuration. I am not quite sure what the best approach is, but I tried it in 
two different ways. One is to create multiple volumes in a single resource like 
the example in the drbd.org documentation and had them configured like the 
following on both nodes:

resource r0 {
        volume 0 {
                device          /dev/drbd0;
                disk            /dev/GROUP0/AOSman;
                flexible-meta-disk      internal;
        }
        volume 1 {
                device          /dev/drbd1;
                disk            /dev/GROUP0/AOScon;
                flexible-meta-disk      internal;
        }
        on FMAOS1 {
                address         10.0.5.65:7788;
        }
        on FMAOS2 {
                address         10.0.5.66:7788;
        }
}

However that yielded the following results when I did a "cat /proc/drbd"

fmadmin@FMAOS1:/etc/drbd.d$ cat /proc/drbd
version: 8.4.3 (api:1/proto:86-101)
srcversion: F97798065516C94BE0F27DC
0: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r-----
    ns:180 nr:0 dw:180 dr:7513 al:5 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:0
1: cs:Connected ro:Secondary/Secondary ds:Diskless/Diskless C r-----
    ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:0


I then tried to define two resource files for two different resources:

fmadmin@FMAOS1:/etc/drbd.d$ sudo cat r0.res
resource r0 {
        on FMAOS1 {
                volume 0 {
                        device          /dev/drbd0;
                        disk            /dev/GROUP0/AOSman;
                        flexible-meta-disk      internal;
                }
                address         10.0.5.65:7788;
        }
        on FMAOS2 {
                volume 0 {
                        device          /dev/drbd0;
                        disk            /dev/GROUP0/AOSman;
                        flexible-meta-disk      internal;
                }
                address         10.0.5.66:7788;
        }
}

fmadmin@FMAOS1:/etc/drbd.d$ sudo cat r1.res
resource r1 {
        on FMAOS1 {
                volume 0 {
                        device          /dev/drbd1;
                        disk            /dev/GROUP0/AOScon;
                        flexible-meta-disk      internal;
                }
                address         10.0.5.65:7789;
        }
        on FMAOS2 {
                volume 0 {
                        device          /dev/drbd1;
                        disk            /dev/GROUP0/AOScon;
                        flexible-meta-disk      internal;
                }
                address         10.0.5.66:7789;
        }
}

That also yielded the following:

fmadmin@FMAOS2:/etc/drbd.d$ cat /proc/drbd
version: 8.4.3 (api:1/proto:86-101)
srcversion: F97798065516C94BE0F27DC
0: cs:Connected ro:Secondary/Primary ds:UpToDate/UpToDate C r-----
    ns:0 nr:180 dw:180 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:0
1: cs:Connected ro:Secondary/Secondary ds:Diskless/Diskless C r-----
    ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:0
node already registered

I am not sure what Diskless/Diskless really means, I suspect that whatever is 
causing that may be causing my issue. Nor, am I sure if either of the two ways 
re correct or if both are a way to do it.

I also see the following when restarting the drbd service:

[
     create res: r0 r1
   prepare disk: r0 r1
    adjust disk: r0 r1:failed(apply-al:255)
     adjust net: r0 r1
]

                                                                         [ OK ]

Any help or pointing to the right direction would be extremely appreciated.

[cid:fm-logodb8643]<http://www.fibermountain.com>
Keith Ouellette

[email protected]


700 West Johnson Avenue
Cheshire, CT06410
www.fibermountain.com   [cid:redline608b9b]     P. (203) 806-4046
C. (860) 810-4877
F. (845) 358-7882
Disclaimer: The information contained in this communication is confidential, 
may be privileged and is intended for the exclusive use of the above named 
addressee(s). If you are not the intended recipient(s), you are expressly 
prohibited from copying, distributing, disseminating, or in any other way using 
any information contained within this communication. If you have received this 
communication in error, please contact the sender by telephone or by response 
via mail. We have taken precautions to minimize the risk of transmitting 
software viruses, but we advise you to carry out your own virus checks on this 
message, as well as any attachments. We cannot accept liability for any loss or 
damage caused by software viruses.

_______________________________________________
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user

Reply via email to