Mailing List Archive: drbd pre4 test / synchro

When the former primary node comes back after a gracefully shutdown
(heartbeat stop, drbd stop), it must be quick synch.
I think this is what happens, but this is not what i can read (output of
drbd script):

#node 1 (primary) : heartbeat stop
#node 1 : drbd stop

#node 2 : becomes primary : ok
#node 2 : writes some blocks on drbd device
#node 2 : cat /proc/drbd
version: 0.6.1-pre4 (api:58/proto:59)
0: cs:WFConnection st:Primary/Unknown ns:0 nr:44 dw:96 dr:36 pe:0
ua:0

#node 1 : drbd start
NODE1:Setting up drbd0...[ OK ]
NODE1:Setting up drbd1...[ OK ]
NODE1:Do you want to abort waiting for other server and make this one
primary?
NODE1:Waiting until drbd0 is up to date (using SyncingAll) abort?
NODE1:Waiting until drbd1 is up to date (using SyncingAll) abort? no
->hmm, fast operation : this does not look like a full sync....
#node 1 : cat /proc/drbd
version: 0.6.1-pre4 (api:58/proto:59)
0: cs:Connected st:Secondary/Primary ns:0 nr:52 dw:52 dr:0 pe:0 ua:0

->Effectively, only 52 blocks were read : synchro was not a full synch,
but just a quick synck

--
Jean-Yves BOUET
EADS Defence and Security Networks
jean-yves.bouet@example.com
01 34 60 86 36

I realized this myself today. -- I will fix it.

BTW, today in the morning I had a few hour to work on DRBD, and
fixed two problems:

*) A very rare race that only affects SMP machines (I think)
"(BUG?) Moving bh=c6e98ba0 to done_ee
drbd3: unlocked bh in ative_ee/sync_ee"

*) Fixed a (very stupid) bug that caused connection drop on idle devices.
(This bug was active if you have more than one device)

I will put out the next pre release rather soon (this week).

-Philipp

* Jean-Yves Bouet - 78636 <jean-yves.bouet@example.com> [011017 09:52]:
> When the former primary node comes back after a gracefully shutdown
> (heartbeat stop, drbd stop), it must be quick synch.
> I think this is what happens, but this is not what i can read (output of
> drbd script):
>
> #node 1 (primary) : heartbeat stop
> #node 1 : drbd stop
>
> #node 2 : becomes primary : ok
> #node 2 : writes some blocks on drbd device
> #node 2 : cat /proc/drbd
> version: 0.6.1-pre4 (api:58/proto:59)
> 0: cs:WFConnection st:Primary/Unknown ns:0 nr:44 dw:96 dr:36 pe:0
> ua:0
>
> #node 1 : drbd start
> NODE1:Setting up drbd0...[ OK ]
> NODE1:Setting up drbd1...[ OK ]
> NODE1:Do you want to abort waiting for other server and make this one
> primary?
> NODE1:Waiting until drbd0 is up to date (using SyncingAll) abort?
> NODE1:Waiting until drbd1 is up to date (using SyncingAll) abort? no
> ->hmm, fast operation : this does not look like a full sync....
> #node 1 : cat /proc/drbd
> version: 0.6.1-pre4 (api:58/proto:59)
> 0: cs:Connected st:Secondary/Primary ns:0 nr:52 dw:52 dr:0 pe:0 ua:0
>
> ->Effectively, only 52 blocks were read : synchro was not a full synch,
> but just a quick synck
>
> --
> Jean-Yves BOUET
> EADS Defence and Security Networks
> jean-yves.bouet@example.com
> 01 34 60 86 36
>
>
>
>
> _______________________________________________
> DRBD-devel mailing list
> DRBD-devel@example.com
> https://lists.sourceforge.net/lists/listinfo/drbd-devel