[DRBD-user] Considerable difference in lower level device sizes: 1975792s vs. 39086082s

[Schmidt, Florian]

Hello everyone, 

after one of my servers crashed I had some issues with broken MBR.

While recovering this I also erased all drbd-partitions and created them
new (with the same size, same order etc.) via fdisk.

Now I wanted to start DRBD again and it won't come up logging the above
message to dmesg.

Here is a part of my drbd.conf:

resource drbd_afd {
        protocol C;


        on saprouter1 {
                device    /dev/drbd0;
                disk      /dev/sda8;
                address   192.168.0.1:7789;
                meta-disk internal;
        }
        on saprouter2 {
                device    /dev/drbd0;
                disk      /dev/sda8;
                address   192.168.0.2:7789;
                meta-disk internal;
        }
}

resource drbd_ftpdata {
        protocol C;

        on saprouter1 {
                device /dev/drbd1;
                disk /dev/sda7;
                address 192.168.0.1:7790;
                meta-disk internal;
        }
        on saprouter2 {
                device /dev/drbd1;
                disk /dev/sda7;
                address 192.168.0.2:7790;
                meta-disk internal;
        }
}

resource drbd_saprouter {
        protocol C;

        on saprouter1 {
                device  /dev/drbd2;
                disk    /dev/sda6;
                address 192.168.0.1:7791;
                meta-disk internal;
        }
        on saprouter2 {
                device  /dev/drbd2;
                disk    /dev/sda6;
                address 192.168.0.2:7791;
                meta-disk internal;
        }
}

As you can see, the drbd-devices always use the same physical devices on
each node.

Now fdisk -l prints this: on both on BOTH nodes:

# fdisk -l

Disk /dev/sda: 159.8 GB, 159865782272 bytes
255 heads, 63 sectors/track, 19435 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1         131     1052226   83  Linux
/dev/sda2             132        3318    25599577+  83  Linux
/dev/sda3            3319        4593    10241437+  83  Linux
/dev/sda4            4594       19435   119218365    5  Extended
/dev/sda5            4594        5103     4096543+  82  Linux swap /
Solaris
/dev/sda6            5104        6320     9775521   83  Linux
/dev/sda7            6321        7537     9775521   83  Linux
/dev/sda8            7538        9970    19543041   83  Linux
/dev/sda9            9971       10093      987966   83  Linux


It's exactly the same on both nodes.

I also created new metadata on the nod with the wrong data, but without
any success.

What can I do, to connect them again?

# /etc/init.d/drbd status
drbd driver loaded OK; device status:
version: 8.2.6 (api:88/proto:86-88)
GIT-hash: 3e69822d3bb4920a8c1bfdf7d647169eba7d2eb4 build by
buildsvn at c5-i386-build, 2008-06-02 10:17:29
m:res             cs            st                   ds
p  mounted  fstype
0:drbd_afd        WFConnection  Secondary/Unknown
Inconsistent/DUnknown  C
1:drbd_ftpdata    WFConnection  Secondary/Unknown    Consistent/DUnknown
C
2:drbd_saprouter  Connected     Secondary/Secondary  UpToDate/UpToDate
C
3:drbd_configs    StandAlone    Secondary/Unknown    Consistent/DUnknown
-

]# /etc/init.d/drbd status
drbd driver loaded OK; device status:
version: 8.2.6 (api:88/proto:86-88)
GIT-hash: 3e69822d3bb4920a8c1bfdf7d647169eba7d2eb4 build by
buildsvn at c5-i386-build, 2008-06-02 10:17:29
m:res             cs            st                   ds
p  mounted  fstype
0:drbd_afd        StandAlone    Primary/Unknown      UpToDate/Outdated
-
1:drbd_ftpdata    StandAlone    Secondary/Unknown    Consistent/DUnknown
-
2:drbd_saprouter  Connected     Secondary/Secondary  UpToDate/UpToDate
C
3:drbd_configs    WFConnection  Primary/Unknown      UpToDate/Outdated
C

Thanks and sorry for this long mail.

Florian