mvolaski at aecom
Jun 25, 2005, 1:03 AM
Post #1 of 3
(1423 views)
Permalink
|
|
[Q] Why does drbd sync only a few resources and apparently at random?
|
|
Hooked up the second system and fired up drbd. Syncing started and in
the right direction :-), but only for a few resources:
version: 0.7.11 (api:77/proto:74)
SVN Revision: 1807 build by root [at] thewarehouse, 2005-06-24 20:20:32
0: cs:StandAlone st:Primary/Unknown ld:Consistent
ns:0 nr:0 dw:1532 dr:6565 al:9 bm:9 lo:0 pe:0 ua:0 ap:0
1: cs:StandAlone st:Primary/Unknown ld:Consistent
ns:0 nr:0 dw:4859352 dr:8062552 al:8228 bm:8355 lo:0 pe:0 ua:0 ap:0
2: cs:SyncSource st:Primary/Secondary ld:Consistent
ns:6615016 nr:0 dw:22740 dr:6726680 al:1662 bm:2192 lo:0 pe:0 ua:0 ap:0
[>...................] sync'ed: 0.9% (715332/721792)M
finish: 24:13:22 speed: 8,320 (7,532) K/sec
3: cs:SyncSource st:Primary/Secondary ld:Consistent
ns:6602616 nr:0 dw:41476 dr:6744512 al:759 bm:1288 lo:0 pe:0 ua:0 ap:0
[>...................] sync'ed: 1.3% (505424/511872)M
finish: 15:17:38 speed: 9,332 (7,508) K/sec
4: cs:StandAlone st:Primary/Unknown ld:Consistent
ns:0 nr:0 dw:22592 dr:43792 al:2704 bm:2831 lo:0 pe:0 ua:0 ap:0
5: cs:StandAlone st:Primary/Unknown ld:Consistent
ns:0 nr:0 dw:17672 dr:22856 al:2064 bm:2191 lo:0 pe:0 ua:0 ap:0
6: cs:StandAlone st:Primary/Unknown ld:Consistent
ns:0 nr:0 dw:26488 dr:72116 al:1812 bm:1939 lo:0 pe:0 ua:0 ap:0
7: cs:StandAlone st:Primary/Unknown ld:Consistent
ns:0 nr:0 dw:35476 dr:63532 al:2184 bm:2311 lo:0 pe:0 ua:0 ap:0
8: cs:StandAlone st:Primary/Unknown ld:Consistent
ns:0 nr:0 dw:19928 dr:42624 al:1709 bm:1836 lo:0 pe:0 ua:0 ap:0
9: cs:StandAlone st:Primary/Unknown ld:Consistent
ns:0 nr:0 dw:73904 dr:215304 al:1251 bm:1378 lo:0 pe:0 ua:0 ap:0
What made it pick these two and why are the others stuck in a
StandAlone state? Everything is in group 2, except for drbd0:
Here's 2, which started syncing automatically:
resource bukauskasdrbd {
protocol C;
incon-degr-cmd "echo '!DRBD! pri on incon-degr' | wall ;
sleep 60 ; halt -f";
startup { wfc-timeout 0; degr-wfc-timeout 120; }
disk { on-io-error detach; }
net { timeout 60; connect-int 10; ping-int 10;
max-buffers 2048; max-epoch-size 2048; }
syncer { rate 8M; group 2; }
on thewarehouse1 {
address 129.98.90.16:7792;
disk /dev/jetstor/bukauskaslv2;
device /dev/drbd2;
meta-disk "internal";
}
on thewarehouse2 {
address 129.98.90.13:7792;
disk /dev/jetstor2/bukauskaslv2;
device /dev/drbd2;
meta-disk "internal";
}
}
Here's 1, which drbd decided to leave in "StandAlone" state:
resource basselldrbd {
protocol C;
incon-degr-cmd "echo '!DRBD! pri on incon-degr' | wall ;
sleep 60 ; halt -f";
startup { wfc-timeout 0; degr-wfc-timeout 120; }
disk { on-io-error detach; }
net { timeout 60; connect-int 10; ping-int 10;
max-buffers 2048; max-epoch-size 2048; }
syncer { rate 8M; group 2; }
on thewarehouse1 {
address 129.98.90.16:7791;
disk /dev/jetstor/basselllv1;
device /dev/drbd1;
meta-disk "internal";
}
on thewarehouse2 {
address 129.98.90.13:7791;
disk /dev/jetstor2/basselllv1;
device /dev/drbd1;
meta-disk "internal";
}
}
I decided to force all to "connect" and indeed that caused
/dev/drbd0, which is group 1, to start syncing and all the others to
enter a PausedSync state.
--
Maurice Volaski, mvolaski [at] aecom
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University
_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user
|
