[Drbd-dev] DRBD8: Stuck in WFBitMapS state even across reboot.

[Montrose, Ernest]

Phil,
This involves Xen Vm's.  I would create one vm, I would then put an i/o
load on there (Something that keeps reading and writing).  I would then
go to the host and do an ifdown on the heartbeat interface in an attempt
to force a split brain situation. I would then do an ifup. And every now
and then this
would happen (not all the time).  When it happens, it survives a reboot.
I actually have not figured out how to get out of it.

I will try to find a more automatic way to reproduce it.

Thanks,

EM--

-----Original Message-----
From: Philipp Reisner [mailto:philipp.reisner at linbit.com] 
Sent: Thursday, November 30, 2006 10:12 AM
To: drbd-dev at linbit.com
Cc: Montrose, Ernest
Subject: Re: [Drbd-dev] DRBD8: Stuck in WFBitMapS state even across
reboot.

Am Montag, 27. November 2006 23:28 schrieb Montrose, Ernest:
> Hi all,
> I am seeing a problem where both nodes get stuck in the WFBitMaps
state
> even across a reboot.
> Dmesg also reveals this on both nodes:
> Drbd0: [drbd0_receiver/4800] sock_sendmsg time expired, ko =
4294967256
> .......
> Drbd0: Split-brain detected, manuall solved. Sync from this node
> Both nodes reports this split brain message.  My configuration for
> device 0 has the following new
> Settings NET:
> rr-conflict violently;
> after-sb-1pri violently-as0p;
> after-sb-2pri violently-as0p;
>
> Thanks for any help.
>

Hi Ernest,

Could you please give us a better description, how we can reproduce this
here ?

-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 :