[DRBD-user] Digest mismatch resulting in "split brain" after (!) automatic reconnect

Lars Ellenberg lars.ellenberg at linbit.com
Mon Feb 21 10:24:13 CET 2011

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


On Mon, Feb 21, 2011 at 10:02:30AM +0100, Raoul Bhatia [IPAX] wrote:
> hi,
> 
> after a couple of days, i can tell that i do not see the described
> problem with
> drbd 8.3.7 and kernel 2.6.32-bpo.5-amd64
> (backports from squeeze to debian lenny)
> 
> > root at c02n01 ~ # cat /proc/drbd
> > version: 8.3.7 (api:88/proto:86-91)
> > srcversion: EE47D8BF18AC166BE219757
> 
> 
> taking a closer look, i also do not see the original error message
> anymore: (Digest mismatch, buffer modified by upper layers during write:
> 0s +4096)

we changed the log message, respectively added the ability to
distinguish between detecting mismatch on the receiving end (previously
possible already), and detecting mismatch on the sending end as well
(previously not checked).

> instead, i now see dmesg like:
> > [197080.750826] block drbd1: Digest integrity check FAILED.
> > [197080.750871] block drbd1: error receiving Data, l: 4136!
> > [197080.750905] block drbd1: peer( Primary -> Unknown ) conn( Connected -> ProtocolError ) pdsk( UpToDate -> DUnknown ) 
> > [197080.750977] block drbd1: asender terminated
> 
> however, the devices correctly get back in sync.
> 
> i'll additionally run a manual verify later on and will report back.
> 
> lars: were you able to extract the logfiles from my original post?

The logs of your original post are completely boring.

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