Le 12/09/2010 19:36, Digimer a écrit :
On 10-09-12 09:31 AM, Sam Przyswa wrote:
Hi,
I use DRBD 8.3.7 on Debian 5.0.6 on Vserver in both side, 2nd machine is
a 1st clone.
There is may drbd.conf:
----------------------------------------------------
global { usage-count yes; }
resource r0 {
protocol B;
startup {
degr-wfc-timeout 120; # 2 minutes
}
disk {
on-io-error detach;
}
net {
}
syncer {
rate 10M;
al-extents 257;
}
on vserver-2 {
device /dev/drbd0;
disk /dev/LVM-1/POSTFIX;
address 88.190.11.187:7789;
meta-disk /dev/LVM-1/meta-1[0];
}
on vserver-1 {
device /dev/drbd0;
disk /dev/LVM-1/POSTFIX-2;
address 88.190.11.244:7789;
meta-disk /dev/LVM-1/meta-1[0];
}
}
----------------------------------------------------
DRBD doesn't believe that the connected disk is UpToDate, so it won't
sync. You need to attach the missing disk. If it's UpToDate, it will
begin to sync. If it isn't, it's more complicated. You will need to
determine what disk is *more* up to date, and then invalidate the other
side.
Now I have the problem if the 1st device is mounted both side connect
well but the primary is Inconsistent/Diskless, and if I *umount* the
device and reload DRBD it become UpToDate/Inconsistent but don't connect
and 1st/Primary give:
version: 8.3.7 (api:88/proto:86-91)
srcversion: EE47D8BF18AC166BE219757
0: cs:WFConnection ro:Primary/Unknown ds:UpToDate/Inconsistent B r----
ns:0 nr:0 dw:0 dr:216 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b
oos:20971520
and the 2nd:
version: 8.3.7 (api:88/proto:86-91)
GIT-hash: ea9e28dbff98e331a62bcbcc63a6135808fe2917 build by r...@buildd,
2010-01-23 08:21:00
0: 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
I don't know what to do
Sam.
_______________________________________________
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user
