Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
I have a problem with drbd 8.0.6
I have setup drbd on top of lvm on two machines with debian etch
(kernel 2.6.18-4-486). I had write access to the common drbd device by
both machines. A change (copy of a new file) on machine A can
immediately be seen on machine B and vice versa.
Now I want to migrate the first machine to production and have installed
a new kernel 2.6.18-5-686. I have recompiled drbd 8.0.6 against the new
kernel sources.
But now changes on machine A are not seen on machine B any more. I have
to detach B and then attach it again in order to get the new state of
the disk. This should not happen - hein?
cat /proc/drbd shows that both sides are in sync after I have copied a
new file to the disk
:
version: 8.0.6 (api:86/proto:86)
SVN Revision: 3048 build by root at sip2, 2007-10-09 23:05:16
0: cs:Connected st:Primary/Primary ds:UpToDate/UpToDate C r---
ns:37 nr:255 dw:292 dr:14 al:0 bm:0 lo:0 pe:0 ua:0 ap:0
resync: used:0/31 hits:0 misses:0 starving:0 dirty:0 changed:0
act_log: used:0/127 hits:37 misses:0 starving:0 dirty:0 changed:0
Here is my drbd.conf. I had to comment the lines with incon-degr-cmd
and group, as starting drbd failed with these commands.
resource r0 {
protocol C;
#incon-degr-cmd "echo '!DRBD! pri on incon-degr' | wall ; sleep 60 ;
halt -f";
startup {
wfc-timeout 0; degr-wfc-timeout 120;
}
net {
allow-two-primaries;
}
disk {
on-io-error detach;
}
syncer {
rate 4M;
#group 3; # sync when r2 is finished syncing.
}
on sip4 {
device /dev/drbd0;
disk /dev/mapper/Data-data1;
address 192.168.178.13:7791;
meta-disk internal;
}
on sip2 {
device /dev/drbd0;
disk /dev/mapper/Data-data1;
address 192.168.178.10:7791;
meta-disk internal;
}
}
Does anyone have an idea?
With kind regards
Peter