[DRBD-user] Primary showing "UpToDate/Inconsistent" Secondary showing "UpToDate/UpToDate"
lars.ellenberg at linbit.com
Thu Jul 22 16:45:28 CEST 2010
On Thu, Jul 22, 2010 at 01:26:24PM +0200, Lars Ellenberg wrote:
> On Thu, Jul 22, 2010 at 11:37:36AM +1000, adamn at eyemedia.com.au wrote:
> > Hi all,
> > I'm sure there is a simple answer to this one..
> > 2 Node cluster with heartbeat.
> > Migrated resources to the secondary node, (with primary online still) all
> > migrated fine.
> > As a test pulled the plug from the secondary node, resources migrated back
> > to primary, no issues at all.
> > Turned the power back on, on the secondary and everything I thought came
> > up ok ,but checking I now have the primary is saying the secondary is
> > inconsistent but the secondary is saying it's UpToDate?
> > How do I fix this?
> This is mainly a cosmetic issue.
> drbdadm disconnect that-resource
> drbdadm connect that-resource
> should clean it up.
> > [ 8512.528680] block drbd1: Began resync as PausedSyncS (will sync 0 KB [0 bits set]).
> > [ 8512.615192] block drbd1: aftr_isp( 1 -> 0 )
> > [ 8513.078766] block drbd1: Resync done (total 1 sec; paused 0 sec; 0 K/sec)
> > [ 8513.078777] block drbd1: conn( PausedSyncS -> Connected ) pdsk( Inconsistent -> UpToDate )
> > [ 8513.078819] block drbd1: pdsk( UpToDate -> Inconsistent ) peer_isp( 1 -> 0 )
> There is a race for "empty" (0 bits set) resyncs and sync dependencies,
> that can lead to this. We have a fix (not yet in public git),
> but it introduces a protocol change, so backporting is not that easy.
I have to correct me here. There was an other race for empty resyncs
causing these symptoms, which has been fixed with 8.3.8
So upgrade to 18.104.22.168 ;-)
: 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