[DRBD-user] DRBD not working. pri node: 1:r0/0 WFConnection Primary/Unknown UpToDate/DUnknown /drbd xfs 194G 33M 194G 1%, sec: 1:r0/0 WFConnection Secondary/Unknown Inconsistent/DUnknown

[aTTi]

I fixed this. I tried directly to /dev/sda and I needed to use the
/dev/mapper/dm-raid device. Now it works this.

The new problem in next level:

config, r0.res:


resource r0 {

        startup {
                wfc-timeout 30;
                outdated-wfc-timeout 20;
                degr-wfc-timeout 30;
        }

        net {
        cram-hmac-alg sha1;
        shared-secret "example";
        after-sb-0pri discard-zero-changes;
        after-sb-1pri discard-secondary;
        after-sb-2pri disconnect;
        rr-conflict disconnect;
        }

        syncer {
        rate 100M;
        verify-alg sha1;
        }

        device /dev/drbd1;
        meta-disk internal;

        on drbdtest1 {
                disk
/dev/mapper/ddf1_4c5349202020202080862682000000004711471100001450p4;
                address 10.1.1.1:7788;

                }

        on drbdtest2 {
                disk
/dev/mapper/ddf1_4c5349202020202080862682000000004711471100001450p3;
                address 10.1.1.2:7788;
        }

        protocol C;

}

Config end.

I run this on both nodes:

drbdadm create-md r0

result:

You want me to create a v08 style flexible-size internal meta data block.
There appears to be a v08 flexible-size internal meta data block
already in place on /dev/mapper/ddf1_xp4 at byte offset 208305909760

Do you really want to overwrite the existing meta-data?
[need to type 'yes' to confirm] yes

md_offset 208305909760
al_offset 208305876992
bm_offset 208299520000

Found some data

 ==> This might destroy existing data! <==

Do you want to proceed?
[need to type 'yes' to confirm] yes

initializing activity log
NOT initializing bitmap
Writing meta data...
New drbd meta data block successfully created.

So it's ok, and same at node 2.

Still on both nodes:

drbdadm up r0
(no response at console)

modprobe drbd
(no response at console)

only on node1:

drbdadm -- --overwrite-data-of-peer primary all
(no response at console)

Then in node1 I format to XFS:

mkfs.xfs /dev/drbd1 -f

then I mounted and copy 1 example file to mounted drbd


node 1:

drbd-overview
 1:r0/0  WFConnection Primary/Unknown UpToDate/DUnknown /drbd xfs 194G
33M 194G 1%

cat /proc/drbd
version: 8.4.5 (api:1/proto:86-101)
GIT-hash: 1d360bde0e095d495786eaeb2a1ac76888e4db96 build by
mockbuild@, 2014-08-17 22:54:26

 1: cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown C r----s
    ns:0 nr:0 dw:101745 dr:2586 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1
wo:f oos:203417500

node 2:

 drbd-overview
 1:r0/0  WFConnection Secondary/Unknown Inconsistent/DUnknown

cat /proc/drbd
version: 8.4.5 (api:1/proto:86-101)
GIT-hash: 1d360bde0e095d495786eaeb2a1ac76888e4db96 build by
mockbuild@, 2014-08-17 22:54:26

 1: cs:WFConnection ro:Secondary/Unknown ds:Inconsistent/DUnknown C r----s
    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:193994980


Versions:

Installed Packages
Name        : drbd84-utils
Arch        : x86_64
Version     : 8.9.1
Release     : 1.el7.elrepo
Size        : 1.3 M
Repo        : installed
>From repo   : elrepo
Summary     : Management utilities for DRBD


Installed Packages
Name        : kmod-drbd84
Arch        : x86_64
Version     : 8.4.5
Release     : 1.el7.elrepo
Size        : 693 k
Repo        : installed
>From repo   : elrepo
Summary     : drbd84 kernel module(s)

End of package info.

What need to do now? What should I do to work this?

Both nodes can access in ssh the other node without password using keys.
Both nodes can ping the other nodes.
Same config for both nodes: (r0.res and default other configs).

I want use drbd with pacemaker + corosync at Centos 7.

Thanks,
aTTi



On Thu, Sep 25, 2014 at 4:50 PM, aTTi <attiuj at gmail.com> wrote: