Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hello,
As already reported by Laurent Simonneau, no problems occur if drbd runs
protocol A. Both protocol B and C kills the primary. However, both
servers are connected directly via GBit ethernet. Isn't this
in contrast to the recommendation to run Protocol A for high latency
networks?
Thanks in advance
Andreas
Gabriel Andreas wrote:
> Hello,for high latency networks
>
> we try to setup DRBD (0.7.10) on top of LVM2 (2.01.0)
> on two Debian 2.4.29-vs1.2.10 (SMP) systems.
>
> After configuration of the drbd resource and initialisation
> of the drbd device on both systems all seems to be running fine
>
> server01> cat /proc/drbd
> version: 0.7.10 (api:77/proto:74)
> SVN Revision: 1743 build by root at pcrz175, 2005-03-02 09:18:52
> 0: cs:Connected st:Primary/Secondary ld:Consistent
> ns:0 nr:8192 dw:8192 dr:0 al:0 bm:4 lo:0 pe:0 ua:0 ap:0
>
> server02> cat /proc/drbd
> version: 0.7.10 (api:77/proto:74)
> SVN Revision: 1743 build by root at pcrz175, 2005-03-02 09:18:52
> 0: cs:Connected st:Secondary/Primary ld:Consistent
> ns:8192 nr:0 dw:0 dr:8192 al:0 bm:2 lo:0 pe:0 ua:0 ap:0
>
>
> But if I try to create an ext3 filesystem on the /dev/drbd0 device,
> following command kills server01:
>
> server01> mke2fs -j -m 0 /dev/drbd0
> mke2fs 1.35 (28-Feb-2004)
> Filesystem label=
> OS type: Linux
> Block size=4096 (log=2)
> Fragment size=4096 (log=2)
> 245760 inodes, 491520 blocks
> 0 blocks (0.00%) reserved for the super user
> First data block=0
> 15 block groups
> 32768 blocks per group, 32768 fragments per group
> 16384 inodes per group
> Superblock backups stored on blocks:
> 32768, 98304, 163840, 229376, 294912
>
> Writing inode tables: done
> Creating journal (8192 blocks): done
> Writing superblocks and filesystem accounting information:
>
>
> And server02 shows following messages:
>
>
> server02> cat /proc/drbd
> version: 0.7.10 (api:77/proto:74)
> SVN Revision: 1743 build by root at pcrz175, 2005-03-02 09:18:52
> 0: cs:WFConnection st:Secondary/Unknown ld:Consistent
> ns:8192 nr:16400 dw:16400 dr:8192 al:0 bm:2 lo:0 pe:0 ua:0 ap:0
>
> server02> dmesg | grep drbd
> drbd: initialised. Version: 0.7.10 (api:77/proto:74)
> drbd: SVN Revision: 1743 build by root at xxxxx, 2005-03-02 09:18:52
> drbd: registered as block device major 147
> drbd0: resync bitmap: bits=491520 words=15360
> drbd0: size = 1920 MB (1966080 KB)
> drbd0: 0 KB marked out-of-sync by on disk bit-map.
> drbd0: No usable activity log found.
> drbd0: drbdsetup [1072]: cstate Unconfigured --> StandAlone
> drbd0: drbdsetup [1075]: cstate StandAlone --> Unconnected
> drbd0: drbd0_receiver [1076]: cstate Unconnected --> WFConnection
> drbd0: drbd0_receiver [1076]: cstate WFConnection --> WFReportParams
> drbd0: Handshake successful: DRBD Network Protocol version 74
> drbd0: Connection established.
> drbd0: I am(S): 1:00000002:00000001:00000002:00000001:01
> drbd0: Peer(S): 1:00000002:00000001:00000001:00000001:11
> drbd0: drbd0_receiver [1076]: cstate WFReportParams --> WFBitMapS
> drbd0: Secondary/Unknown --> Secondary/Secondary
> drbd0: drbd0_receiver [1076]: cstate WFBitMapS --> SyncSource
> drbd0: Resync started as SyncSource (need to sync 8192 KB [2048 bits set]).
> drbd0: Resync done (total 1 sec; paused 0 sec; 8192 K/sec)
> drbd0: drbd0_worker [1073]: cstate SyncSource --> Connected
> drbd0: Secondary/Secondary --> Secondary/Primary
> drbd0: drbd0_asender [1077]: cstate Connected --> Timeout
> drbd0: short sent WriteAck size=32 sent=8
> drbd0: short sent BarrierAck size=16 sent=-1001
> drbd0: asender terminated
> drbd0: error receiving Barrier, l: 8!
> drbd0: worker terminated
> drbd0: unacked_cnt = 75
> drbd0: drbd0_receiver [1076]: cstate Timeout --> Unconnected
> drbd0: Connection lost.
> drbd0: drbd0_receiver [1076]: cstate Unconnected --> WFConnection
>
> --------------------
>
> drbd.conf on both systems
>
> #############
> resource "zeo" {
> protocol C;
> incon-degr-cmd "echo '!DRBD! pri on incon-degr' | wall ; sleep 60 halt
> -f";
> startup {
> }
> disk {
> on-io-error detach;
> }
> net {
> }
> syncer {
> rate 50M;
> group 0;
> al-extents 257;
> }
> on server01 {
> device /dev/drbd0;
> disk /dev/zeo_vg/zeo_lv;
> address 10.0.0.1:7800;
> meta-disk internal;
> }
> on server02 {
> device /dev/drbd0;
> disk /dev/zeo_vg/zeo_lv;
> address 10.0.0.2:7800;
> meta-disk internal;
> }
> }
> ##############
>
>
> The logical volume configuration on both systems
>
> server01/02>lvdisplay
> --- Logical volume ---
> LV Name /dev/zeo_vg/zeo_lv
> VG Name zeo_vg
> LV UUID H8Ffeh-znZi-jE7x-cYtF-4Hch-ddRL-NyMDHp
> LV Write Access read/write
> LV Status available
> # open 4
> LV Size 2.00 GB
> Current LE 512
> Segments 1
> Allocation inherit
> Read ahead sectors 0
> Block device 254:7
>
> ##############
>
>
> Any hints?
>
> Thank You
> Andreas