[DRBD-user] one of drbd disk need full resync after reboot

Lars Ellenberg lars.ellenberg at linbit.com
Thu Jun 4 12:30:22 CEST 2009

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

On Wed, Jun 03, 2009 at 11:38:18PM +0700, chatchai jantaraprim wrote:
> On Wed, Jun 3, 2009 at 2:13 PM, Lars Ellenberg
> <lars.ellenberg at linbit.com> wrote:
> > On Wed, Jun 03, 2009 at 12:51:22PM +0700, chatchai jantaraprim wrote:
> >> >> May 28 13:21:09 nnksvr01 kernel: [  150.504885] drbd6: No resync, but
> >> >> 44522728 bits in bitmap!
> >
> > btw, is anything about "full sync required" or other "strange" messages
> > on the other node?
>    Ah, yes, there is "full sync required" message on the other node.
> drbd6: drbd_sync_handshake:
> drbd6: self DA26B785F0FD01C9:0000000000000000:2951B01A84735B7B:F7668094BF050519
> drbd6: peer 2951B01A84735B7A:0000000000000000:E56A0B0B69CA4098:B4B5CF85BFA1686C
> drbd6: uuid_compare()=2 by rule 8
> drbd6: Becoming sync source due to disk states.
> drbd6: Writing the whole bitmap, full sync required after drbd_sync_handshake.
> drbd6: 170 GB (44522728 bits) marked out-of-sync by on disk bit-map.
>    The log on the other node during the same period is in attached
> file. Since I'm not sure
> how to make gmail not to wrap line.

this did indeed help me understand what was going on.
two interessting distributed races involved.
I think I have fixed it, we will try to reproduce, and then confirm that
my proposed patch to make those races harmless actually fixes the issue
(and causes no collateral damage).

Thanks for reporting this.

: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
please don't Cc me, but send to list   --   I'm subscribed

More information about the drbd-user mailing list