[DRBD-user] sync doesn't start

Philipp Reisner philipp.reisner at linbit.com
Mon Nov 29 16:02:10 CET 2004

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


[...]

> Proc1:~ # drbdadm invalidate all
> ioctl(,INVALIDATE,) failed: Operation now in progress
> Only in 'Connected' cstate possible.
> Command '/sbin/drbdsetup /dev/drbd0 invalidate' terminated with exit code
> 20 drbdsetup exited with code 20
>
> Proc1:~ # cat /proc/drbd
> version: 0.7.4 (api:76/proto:74)
> SVN Revision: 1539 build by lmb at chip, 2004-09-14 10:21:07
>  0: cs:Connected st:Primary/Secondary ld:Consistent
>     ns:3004 nr:0 dw:3004 dr:4600 al:37 bm:4024 lo:0 pe:0 ua:0 ap:0
>
>
> Ok, fair enough, we don't want to invalidate the primary side.
> Try do the same thing on the other side.
>

Right, it is not allowed to invalidate a primary node.

>
> Proc2:~ # cat /proc/drbd
> version: 0.7.4 (api:76/proto:74)
> SVN Revision: 1539 build by lmb at chip, 2004-09-14 10:21:07
>  0: cs:Connected st:Secondary/Primary ld:Consistent
>     ns:0 nr:3004 dw:3004 dr:0 al:0 bm:4024 lo:0 pe:0 ua:0 ap:0
>
> Proc2:~ # drbdadm invalidate all
>
> Proc2:~ # cat /proc/drbd
> version: 0.7.4 (api:76/proto:74)
> SVN Revision: 1539 build by lmb at chip, 2004-09-14 10:21:07
>  0: cs:WFBitMapT st:Secondary/Primary ld:Inconsistent
>     ns:0 nr:3004 dw:3004 dr:0 al:0 bm:8048 lo:0 pe:0 ua:0 ap:0
>
> Proc2: /var/log/messages
> Nov 26 18:02:15 Proc2 kernel: drbd0: drbdsetup [3415]: cstate Connected -->
> WFBitMapT Nov 26 18:02:16 Proc2 kernel: drbd0: 65928176 KB now marked
> out-of-sync by on disk bit-map.
>
>
> Looks ok, the secondary has initiated the sync. Now let's look at the
> primary side.
>
>
> Proc1:~ # cat /proc/drbd
> version: 0.7.4 (api:76/proto:74)
> SVN Revision: 1539 build by lmb at chip, 2004-09-14 10:21:07
>  0: cs:Connected st:Primary/Secondary ld:Consistent
>     ns:3004 nr:0 dw:3004 dr:4600 al:37 bm:4024 lo:0 pe:0 ua:0 ap:0
>
> Proc1: /var/log/messages
> (contains nothing new)
>
>
> This is where the problem starts. Even if the nodes are connected and all,
> the primary node has no idea the secondary node wants to synchronize.
>

Has been fixed in 0.7.6, from the changelog:

 * "drbdadm invalidate [res]" was not working correct, while
   "drbdadm invalidate_remote [res]" works. Fixed the former.


-phil

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



More information about the drbd-user mailing list