[SOLVED] DRBD with multiple resources

NetEng1 · 11-18-2014, 05:35 AM

I am trying to setup two systems with two replicated volumes. Each volume supporting their own application. 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:

Code:

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”

Code:

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:

Code:

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:

Code:

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 are the correct way to configure this or if both are acceptable ways to configure it.

I also see the following when restarting the drbd service:

Code:

[
     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.

NetEng1 · 11-19-2014, 09:02 PM

Okay, the issue was that drbd did not like the volume format created by system-config-lvm. I had to "zero" out the partition, then I was able to create the meta data then start drbd with the added resource. I ended up by using the separate file approach.