[DRBD-user] DRBD 0.8rc2 deadlock "WFBitMap" ?

Philipp Reisner philipp.reisner at linbit.com
Mon Jan 22 09:50:36 CET 2007


Am Montag, 22. Januar 2007 00:33 schrieb Ralf Schenk:
> Hello
>
> After successfully creating an 2 DRBD Devices on top of LVM, I tried
> different net settings for performance optimisation.
>
> I always edited the configuration file, copied it to the remote host and
> issued a "drbdadm adjust RESSOURCNAME".
>
> Yesterday my ressource "vm02" stopped working in a state "WFBitMap"
> after a "drbdadm adjust vm02"
>
> Today I tested with the remaining ressource "vm01" and after a few
> changes and benchmarking this ressource stopped working, too.
>
> my cat /proc/drbd shows:
> version: 8.0rc2 (api:86/proto:86)
> SVN Revision: 2704 build by root at server, 2007-01-18 16:05:48
>  0: cs:WFBitMapS st:Primary/Secondary ds:UpToDate/UpToDate C r---
>     ns:0 nr:0 dw:0 dr:0 al:0 bm:127 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:0 misses:0 starving:0 dirty:0 changed:0
>  1: cs:WFBitMapT st:Secondary/Primary ds:UpToDate/UpToDate C r---
>     ns:0 nr:0 dw:0 dr:0 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:0 misses:0 starving:0 dirty:0 changed:0
>
>
> I rebooted and tried to outdate the secondary(s) to do a full resync but
> that didn't work.
>
> What can I do to recover from this situation ?

drbdadm down all ; drbdadm up all

But, please post your excerpts from the kernel logs (of both machines) 
of the incident.
And tell us if the clocks of the machines are in sync (with NTP), or
what time difference you have there.

-Phil
-- 
: Dipl-Ing Philipp Reisner                      Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH          Fax +43-1-8178292-82 :
: Vivenotgasse 48, 1120 Vienna, Austria        http://www.linbit.com :



More information about the drbd-user mailing list