Problem with DRBD on Proxmox 1.3

docent

Renowned Member
Jul 23, 2009
96
1
73
I can't configure DRBD on Proxmox 1.3.

===== drbd.conf on both hosts:
global {
usage-count yes;
}

common {
syncer { rate 100M; }
}

resource w2k8 {
protocol C;
startup {
wfc-timeout 20;
degr-wfc-timeout 20;
}
net {
allow-two-primaries;
}
syncer {
rate 100M;
al-extents 257;
}
on pm1
{
address 10.1.1.141:7803;
device /dev/drbd3;
disk /dev/pve/w2k8;
meta-disk /dev/pve/w2k8-meta[0];
}
on pm2
{
address 10.1.1.142:7803;
device /dev/drbd3;
disk /dev/pve/w2k8;
meta-disk /dev/pve/w2k8-meta[0];
}
}

After starting DRBD on both hosts I have:
===== On host 1 (named pm1):
pm1:/var/log# cat /proc/drbd
version: 8.3.1 (api:88/proto:86-89)
GIT-hash: fd40f4a8f9104941537d1afc8521e584a6d3003c build by root@oahu, 2009-06-02 08:01:37

3: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown r---
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:20971520

===== On host 2 (named pm2):
pm2:/etc# cat /proc/drbd
version: 8.3.1 (api:88/proto:86-89)
GIT-hash: fd40f4a8f9104941537d1afc8521e584a6d3003c build by root@oahu, 2009-06-02 08:01:37

3: cs:WFConnection ro:Secondary/Unknown ds:UpToDate/Inconsistent 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:b oos:20971520

===== In kern.log on pm1:
Jul 23 11:36:10 pm1 kernel: drbd: initialised. Version: 8.3.1 (api:88/proto:86-89)
Jul 23 11:36:10 pm1 kernel: drbd: GIT-hash: fd40f4a8f9104941537d1afc8521e584a6d3003c build by root@oahu, 2009-06-02 08:01:37
Jul 23 11:36:10 pm1 kernel: drbd: registered as block device major 147
Jul 23 11:36:10 pm1 kernel: drbd: minor_table @ 0xffff810155773100
Jul 23 11:36:10 pm1 kernel: drbd3: disk( Diskless -> Attaching )
Jul 23 11:36:10 pm1 kernel: drbd3: Starting worker thread (from cqueue/5 [3769])
Jul 23 11:36:10 pm1 kernel: drbd3: No usable activity log found.
Jul 23 11:36:10 pm1 kernel: drbd3: Method to ensure write ordering: barrier
Jul 23 11:36:10 pm1 kernel: drbd3: max_segment_size ( = BIO size ) = 32768
Jul 23 11:36:10 pm1 kernel: drbd3: drbd_bm_resize called with capacity == 41943040
Jul 23 11:36:10 pm1 kernel: drbd3: resync bitmap: bits=5242880 words=81920
Jul 23 11:36:10 pm1 kernel: drbd3: size = 20 GB (20971520 KB)
Jul 23 11:36:10 pm1 kernel: drbd3: recounting of set bits took additional 0 jiffies
Jul 23 11:36:10 pm1 kernel: drbd3: 20 GB (5242880 bits) marked out-of-sync by on disk bit-map.
Jul 23 11:36:10 pm1 kernel: drbd3: disk( Attaching -> Inconsistent )
Jul 23 11:36:10 pm1 kernel: drbd3: Barriers not supported on meta data device - disabling
Jul 23 11:36:10 pm1 kernel: drbd3: conn( StandAlone -> Unconnected )
Jul 23 11:36:10 pm1 kernel: drbd3: Starting receiver thread (from drbd3_worker [9915])
Jul 23 11:36:10 pm1 kernel: drbd3: receiver (re)started
Jul 23 11:36:10 pm1 kernel: drbd3: conn( Unconnected -> WFConnection )
Jul 23 11:36:10 pm1 kernel: drbd3: Handshake successful: Agreed network protocol version 89
Jul 23 11:36:10 pm1 kernel: drbd3: conn( WFConnection -> WFReportParams )
Jul 23 11:36:10 pm1 kernel: drbd3: Starting asender thread (from drbd3_receiver [9924])
Jul 23 11:36:10 pm1 kernel: drbd3: data-integrity-alg: <not-used>
Jul 23 11:36:10 pm1 kernel: drbd3: drbd_sync_handshake:
Jul 23 11:36:10 pm1 kernel: drbd3: self 4C8D7EA710D934CE:0000000000000000:0000000000000000:0000000000000000 bits:5242880 flags:0
Jul 23 11:36:10 pm1 kernel: drbd3: peer 1DC248591B1452C2:4C8D7EA710D934CF:050C6480FDBB8032:F6BB63A13F266AAE bits:5242880 flags:0
Jul 23 11:36:10 pm1 kernel: drbd3: uuid_compare()=-1 by rule 5
Jul 23 11:36:10 pm1 kernel: drbd3: Becoming sync target due to disk states.
Jul 23 11:36:10 pm1 kernel: drbd3: peer( Unknown -> Secondary ) conn( WFReportParams -> WFBitMapT ) pdsk( DUnknown -> UpToDate )
Jul 23 11:36:10 pm1 kernel: drbd3: conn( WFBitMapT -> WFSyncUUID )
Jul 23 11:36:10 pm1 kernel: drbd3: helper command: /sbin/drbdadm before-resync-target minor-3
Jul 23 11:36:10 pm1 kernel: drbd3: helper command: /sbin/drbdadm before-resync-target minor-3 exit code 3 (0x300)
Jul 23 11:36:10 pm1 kernel: drbd3: before-resync-target handler returned 3, dropping connection.
Jul 23 11:36:10 pm1 kernel: drbd3: peer( Secondary -> Unknown ) conn( WFSyncUUID -> Disconnecting ) pdsk( UpToDate -> DUnknown )
Jul 23 11:36:10 pm1 kernel: drbd3: asender terminated
Jul 23 11:36:10 pm1 kernel: drbd3: Terminating asender thread
Jul 23 11:36:10 pm1 kernel: drbd3: Connection closed
Jul 23 11:36:10 pm1 kernel: drbd3: conn( Disconnecting -> StandAlone )
Jul 23 11:36:10 pm1 kernel: drbd3: receiver terminated
Jul 23 11:36:10 pm1 kernel: drbd3: Terminating receiver thread

===== In kern.log on pm2:
Jul 23 11:36:10 pm2 kernel: drbd: initialised. Version: 8.3.1 (api:88/proto:86-89)
Jul 23 11:36:10 pm2 kernel: drbd: GIT-hash: fd40f4a8f9104941537d1afc8521e584a6d3003c build by root@oahu, 2009-06-02 08:01:37
Jul 23 11:36:10 pm2 kernel: drbd: registered as block device major 147
Jul 23 11:36:10 pm2 kernel: drbd: minor_table @ 0xffff8101520f4c00
Jul 23 11:36:10 pm2 kernel: drbd3: disk( Diskless -> Attaching )
Jul 23 11:36:10 pm2 kernel: drbd3: Starting worker thread (from cqueue/0 [3733])
Jul 23 11:36:10 pm2 kernel: drbd3: No usable activity log found.
Jul 23 11:36:10 pm2 kernel: drbd3: Method to ensure write ordering: barrier
Jul 23 11:36:10 pm2 kernel: drbd3: max_segment_size ( = BIO size ) = 32768
Jul 23 11:36:10 pm2 kernel: drbd3: drbd_bm_resize called with capacity == 41943040
Jul 23 11:36:10 pm2 kernel: drbd3: resync bitmap: bits=5242880 words=81920
Jul 23 11:36:10 pm2 kernel: drbd3: size = 20 GB (20971520 KB)
Jul 23 11:36:10 pm2 kernel: drbd3: recounting of set bits took additional 0 jiffies
Jul 23 11:36:10 pm2 kernel: drbd3: 20 GB (5242880 bits) marked out-of-sync by on disk bit-map.
Jul 23 11:36:10 pm2 kernel: drbd3: disk( Attaching -> UpToDate ) pdsk( DUnknown -> Outdated )
Jul 23 11:36:10 pm2 kernel: drbd3: Barriers not supported on meta data device - disabling
Jul 23 11:36:10 pm2 kernel: drbd3: conn( StandAlone -> Unconnected )
Jul 23 11:36:10 pm2 kernel: drbd3: Starting receiver thread (from drbd3_worker [9738])
Jul 23 11:36:10 pm2 kernel: drbd3: receiver (re)started
Jul 23 11:36:10 pm2 kernel: drbd3: conn( Unconnected -> WFConnection )
Jul 23 11:36:10 pm2 kernel: drbd3: Handshake successful: Agreed network protocol version 89
Jul 23 11:36:10 pm2 kernel: drbd3: conn( WFConnection -> WFReportParams )
Jul 23 11:36:10 pm2 kernel: drbd3: Starting asender thread (from drbd3_receiver [9745])
Jul 23 11:36:10 pm2 kernel: drbd3: data-integrity-alg: <not-used>
Jul 23 11:36:10 pm2 kernel: drbd3: drbd_sync_handshake:
Jul 23 11:36:10 pm2 kernel: drbd3: self 1DC248591B1452C2:4C8D7EA710D934CF:050C6480FDBB8032:F6BB63A13F266AAE bits:5242880 flags:0
Jul 23 11:36:10 pm2 kernel: drbd3: peer 4C8D7EA710D934CE:0000000000000000:0000000000000000:0000000000000000 bits:5242880 flags:0
Jul 23 11:36:10 pm2 kernel: drbd3: uuid_compare()=1 by rule 7
Jul 23 11:36:10 pm2 kernel: drbd3: Becoming sync source due to disk states.
Jul 23 11:36:10 pm2 kernel: drbd3: peer( Unknown -> Secondary ) conn( WFReportParams -> WFBitMapS ) pdsk( Outdated -> Inconsistent )
Jul 23 11:36:10 pm2 kernel: drbd3: conn( WFBitMapS -> SyncSource )
Jul 23 11:36:10 pm2 kernel: drbd3: Began resync as SyncSource (will sync 20971520 KB [5242880 bits set]).
Jul 23 11:36:10 pm2 kernel: drbd3: meta connection shut down by peer.
Jul 23 11:36:10 pm2 kernel: drbd3: peer( Secondary -> Unknown ) conn( SyncSource -> NetworkFailure )
Jul 23 11:36:10 pm2 kernel: drbd3: asender terminated
Jul 23 11:36:10 pm2 kernel: drbd3: Terminating asender thread
Jul 23 11:36:10 pm2 kernel: drbd3: sock was shut down by peer
Jul 23 11:36:10 pm2 kernel: drbd3: short read expecting header on sock: r=0
Jul 23 11:36:10 pm2 kernel: drbd3: Connection closed
Jul 23 11:36:10 pm2 kernel: drbd3: conn( NetworkFailure -> Unconnected )
Jul 23 11:36:10 pm2 kernel: drbd3: receiver terminated
Jul 23 11:36:10 pm2 kernel: drbd3: Restarting receiver thread
Jul 23 11:36:10 pm2 kernel: drbd3: receiver (re)started
Jul 23 11:36:10 pm2 kernel: drbd3: conn( Unconnected -> WFConnection )

When I installed Ubuntu 9.04 at these computers, DRBD has started to work without problems.

I can't find solutions to this problem on the Internet.

Help me, pls!
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!