[DRBD-user] drbd and secondary while primary down

Tim Hibbard hibbard at research.ohiou.edu
Mon Jul 18 16:49:36 CEST 2005

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


This is the logfile from leo2.  Previous email had log file from leo1. Sorry 
about that.

LEO2 logfile:
drbd3: drbd3_receiver [2516]: cstate WFConnection --> WFReportParams
drbd3: Handshake successful: DRBD Network Protocol version 74
drbd3: Connection established.
drbd3: I am(S): 1:00000002:00000002:00000049:00000007:00
drbd3: Peer(S): 1:00000002:00000002:0000004b:00000006:10
drbd3: drbd3_receiver [2516]: cstate WFReportParams --> WFBitMapT
drbd3: Secondary/Unknown --> Secondary/Secondary
drbd3: drbd3_receiver [2516]: cstate WFBitMapT --> SyncTarget
drbd3: Resync started as SyncTarget (need to sync 81928 KB [20482 bits set]).
drbd3: Resync done (total 2 sec; paused 0 sec; 40964 K/sec)
drbd3: drbd3_worker [7749]: cstate SyncTarget --> Connected
drbd3: Secondary/Secondary --> Secondary/Primary


Thanks in advance

Tim Hibbard

On Monday 18 July 2005 10:11 am, Lars Ellenberg wrote:
> / 2005-07-18 08:50:05 -0400
>
> \ Tim Hibbard:
> > While NodeB is active I deleted a directory on the block device,
> > excepting the change to also reflect when NodeA became available again. 
> > Instead when NodeA comes alive again it seems to sync NodeA to NodeB
> > block.  When heartbeat does its recovery the directory and all it's
> > contents are found on both block devices again.  As a note, while NodeB
> > is primary, /proc/drbd does show Primary/UnKnown and mount shows
> > /dev/drbd3 mounted to /usr/local/leo.
>
> so. first, is it correct that you basically did:
> | leo1# grep "^ 3: cs:" /proc/drbd
> |  3: cs:Connected st:Primary/Secondary ld:Consistent
> |
> | leo1# halt
> |
> | ... automatic failover by heartbeat to leo2 ...
> |
> | leo2# grep "^ 3: cs:" /proc/drbd
> |  3: cs:WFConnettion st:Primary/Unknown ld:Consistent
> |
> | leo2# rm -r /mountpoint/of/drbd3/some/previously/existing/directory
> |
> | ... switch on leo1 again ...
> |
> | leo2# grep "^ 3: cs:" /proc/drbd
> |  3: cs:SyncSource st:Primary/Secondary ld:Consistent
> |
> | ...
> |
> | leo2# grep "^ 3: cs:" /proc/drbd
> |  3: cs:Connected st:Primary/Secondary ld:Consistent
> |
> | leo2# ..../hb_standby
> |
> | ... operator triggered heartbeat failback to leo1 again ...
> |
> | leo1# grep "^ 3: cs:" /proc/drbd
> |  3: cs:Connected st:Primary/Secondary ld:Consistent
> |
> | leo1# ln -l /mountpoint/of/drbd3/some/previously/existing/directory
> |   [ lists contents of supposedly removed directory ]
>
> if that is indeed what has happend, I'd be interessted in the syslog/kernel
> logs, to be able to explain to you why what happened was expected, even
> though you expected otherwise ;-)
>
> especially the lines looking similar to
>
>   kernel: drbd0: drbd0_receiver [5482]: cstate WFConnection -->
> WFReportParams kernel: drbd0: Handshake successful: DRBD Network Protocol
> version 74 kernel: drbd0: Connection established.
>   kernel: drbd0: I am(P): 1:00000002:00000001:00000004:00000001:10
>   kernel: drbd0: Peer(S): 1:00000002:00000001:00000003:00000001:01
>   kernel: drbd0: drbd0_receiver [5482]: cstate WFReportParams --> WFBitMapS
>   kernel: drbd0: Primary/Unknown --> Primary/Secondary
>   kernel: drbd0: drbd0_receiver [5482]: cstate WFBitMapS --> SyncSource
>   kernel: drbd0: Resync started as SyncSource (need to sync 156640 KB
> [39160 bits set]). kernel: drbd0: Resync done (total 7 sec; paused 0 sec;
> 22377 K/sec)
>
> (including hostname and timestamp, obviously)
>
> if you did something else, please specify.
>
> cheers,
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20050718/cd5502e6/attachment.pgp>


More information about the drbd-user mailing list