Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
* [Drbd-dev] DRBD8: rr-conflict violently breaks sync states.
@ 2006-12-01 22:10 Montrose, Ernest
  2006-12-04 10:28 ` Philipp Reisner
  0 siblings, 1 reply; 5+ messages in thread
From: Montrose, Ernest @ 2006-12-01 22:10 UTC (permalink / raw)
  To: drbd-dev


If "rr-conflict vilently;" is present in /etc/drbd.conf then the drbd
volumes will not sync completely. Some of them ends up in :
cs: Connected:St: secondary/Secondary:ds: Inconsistent/Inconsistent

These states are on both nodes. 

It seems like this rr-conflict violently is not fully implemented.

^ permalink raw reply	[flat|nested] 5+ messages in thread
* RE: [Drbd-dev] DRBD8: rr-conflict violently breaks sync states.
@ 2006-12-04 13:52 Montrose, Ernest
  0 siblings, 0 replies; 5+ messages in thread
From: Montrose, Ernest @ 2006-12-04 13:52 UTC (permalink / raw)
  To: Philipp Reisner, drbd-dev

Phil,
Thanks for looking at this.  I am still investigating as well.  But here
is what's in the kernel log on both nodes.

Kernel message buffer log for a device that won't sync:
Node1:
drbd2: disk( Diskless -> Attaching )
drbd2: No usable activity log found.
drbd2: max_segment_size ( = BIO size ) = 32768
drbd2: drbd_bm_resize called with capacity == 30735368
drbd2: resync bitmap: bits=3841921 words=120062
drbd2: size = 14 GB (15367684 KB)
drbd2: writing of bitmap took 19 jiffies
drbd2: 14 GB marked out-of-sync by on disk bit-map.
drbd2: 15367684 KB now marked out-of-sync by on disk bit-map.
drbd2: reading of bitmap took 16 jiffies
drbd2: recounting of set bits took additional 1 jiffies
drbd2: 14 GB marked out-of-sync by on disk bit-map.
drbd2: disk( Attaching -> Inconsistent )
drbd2: Writing meta data super block now.
drbd2: conn( StandAlone -> Unconnected )
drbd2: receiver (re)started
drbd2: conn( Unconnected -> WFConnection )
drbd2: conn( WFConnection -> WFReportParams )
drbd2: Handshake successful: DRBD Network Protocol version 85
drbd2: No resync, but bits in bitmap!
drbd2: peer( Unknown -> Secondary ) conn( WFReportParams -> Connected )
pdsk( DUnknown -> Inconsistent )
drbd2: Writing meta data super block now.
drbd2: aftr_isp( 0 -> 1 )
drbd2: No resync, but bits in bitmap!
drbd2: peer_isp( 0 -> 1 )
drbd2: aftr_isp( 1 -> 0 )
drbd2: No resync, but bits in bitmap!
drbd2: peer_isp( 1 -> 0 )


On node2:
drbd2: disk( Diskless -> Attaching )
drbd2: No usable activity log found.
drbd2: max_segment_size ( = BIO size ) = 32768
drbd2: drbd_bm_resize called with capacity == 30735368
drbd2: resync bitmap: bits=3841921 words=120062
drbd2: size = 14 GB (15367684 KB)
drbd2: writing of bitmap took 19 jiffies
drbd2: 14 GB marked out-of-sync by on disk bit-map.
drbd2: 15367684 KB now marked out-of-sync by on disk bit-map.
drbd2: reading of bitmap took 12 jiffies
drbd2: recounting of set bits took additional 1 jiffies
drbd2: 14 GB marked out-of-sync by on disk bit-map.
drbd2: disk( Attaching -> Inconsistent )
drbd2: Writing meta data super block now.
drbd2: conn( StandAlone -> Unconnected )
drbd2: receiver (re)started
drbd2: conn( Unconnected -> WFConnection )
drbd2: conn( WFConnection -> WFReportParams )
drbd2: Handshake successful: DRBD Network Protocol version 85
drbd2: No resync, but bits in bitmap!
drbd2: peer( Unknown -> Secondary ) conn( WFReportParams -> Connected )
pdsk( DUnknown -> Inconsistent )
drbd2: Writing meta data super block now.
drbd2: aftr_isp( 0 -> 1 )
drbd2: No resync, but bits in bitmap!
drbd2: peer_isp( 0 -> 1 )
drbd2: No resync, but bits in bitmap!
drbd2: peer_isp( 1 -> 0 )
drbd2: aftr_isp( 1 -> 0 )

-----Original Message-----
From: drbd-dev-bounces@linbit.com [mailto:drbd-dev-bounces@linbit.com]
On Behalf Of Philipp Reisner
Sent: Monday, December 04, 2006 5:29 AM
To: drbd-dev@linbit.com
Subject: Re: [Drbd-dev] DRBD8: rr-conflict violently breaks sync states.

Am Freitag, 1. Dezember 2006 23:10 schrieb Montrose, Ernest:
> If "rr-conflict vilently;" is present in /etc/drbd.conf then the drbd
> volumes will not sync completely. Some of them ends up in :
> cs: Connected:St: secondary/Secondary:ds: Inconsistent/Inconsistent
>
> These states are on both nodes.
>
> It seems like this rr-conflict violently is not fully implemented.


Hi Ernest,

Actually it is. Could you grep in the kernel-logfile for all messages of
the devices that ended up in that state. Preferrable from both nodes.

Thanks!

-phil
-- 
: Dipl-Ing Philipp Reisner                      Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH          Fax +43-1-8178292-82 :
: Vivenotgasse 48, 1120 Vienna, Austria        http://www.linbit.com :
_______________________________________________
drbd-dev mailing list
drbd-dev@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-dev

^ permalink raw reply	[flat|nested] 5+ messages in thread
* RE: [Drbd-dev] DRBD8: rr-conflict violently breaks sync states.
@ 2006-12-04 15:08 Montrose, Ernest
  0 siblings, 0 replies; 5+ messages in thread
From: Montrose, Ernest @ 2006-12-04 15:08 UTC (permalink / raw)
  To: Montrose, Ernest, Philipp Reisner, drbd-dev

Phil,
I see some errors in our install log for the nodes. Let me investigate
those before you dig deep into this.  It might be our fault here..:)
Stay tuned.

Thanks,

EM--

-----Original Message-----
From: drbd-dev-bounces@linbit.com [mailto:drbd-dev-bounces@linbit.com]
On Behalf Of Montrose, Ernest
Sent: Monday, December 04, 2006 8:53 AM
To: Philipp Reisner; drbd-dev@linbit.com
Subject: RE: [Drbd-dev] DRBD8: rr-conflict violently breaks sync states.

Phil,
Thanks for looking at this.  I am still investigating as well.  But here
is what's in the kernel log on both nodes.

Kernel message buffer log for a device that won't sync:
Node1:
drbd2: disk( Diskless -> Attaching )
drbd2: No usable activity log found.
drbd2: max_segment_size ( = BIO size ) = 32768
drbd2: drbd_bm_resize called with capacity == 30735368
drbd2: resync bitmap: bits=3841921 words=120062
drbd2: size = 14 GB (15367684 KB)
drbd2: writing of bitmap took 19 jiffies
drbd2: 14 GB marked out-of-sync by on disk bit-map.
drbd2: 15367684 KB now marked out-of-sync by on disk bit-map.
drbd2: reading of bitmap took 16 jiffies
drbd2: recounting of set bits took additional 1 jiffies
drbd2: 14 GB marked out-of-sync by on disk bit-map.
drbd2: disk( Attaching -> Inconsistent )
drbd2: Writing meta data super block now.
drbd2: conn( StandAlone -> Unconnected )
drbd2: receiver (re)started
drbd2: conn( Unconnected -> WFConnection )
drbd2: conn( WFConnection -> WFReportParams )
drbd2: Handshake successful: DRBD Network Protocol version 85
drbd2: No resync, but bits in bitmap!
drbd2: peer( Unknown -> Secondary ) conn( WFReportParams -> Connected )
pdsk( DUnknown -> Inconsistent )
drbd2: Writing meta data super block now.
drbd2: aftr_isp( 0 -> 1 )
drbd2: No resync, but bits in bitmap!
drbd2: peer_isp( 0 -> 1 )
drbd2: aftr_isp( 1 -> 0 )
drbd2: No resync, but bits in bitmap!
drbd2: peer_isp( 1 -> 0 )


On node2:
drbd2: disk( Diskless -> Attaching )
drbd2: No usable activity log found.
drbd2: max_segment_size ( = BIO size ) = 32768
drbd2: drbd_bm_resize called with capacity == 30735368
drbd2: resync bitmap: bits=3841921 words=120062
drbd2: size = 14 GB (15367684 KB)
drbd2: writing of bitmap took 19 jiffies
drbd2: 14 GB marked out-of-sync by on disk bit-map.
drbd2: 15367684 KB now marked out-of-sync by on disk bit-map.
drbd2: reading of bitmap took 12 jiffies
drbd2: recounting of set bits took additional 1 jiffies
drbd2: 14 GB marked out-of-sync by on disk bit-map.
drbd2: disk( Attaching -> Inconsistent )
drbd2: Writing meta data super block now.
drbd2: conn( StandAlone -> Unconnected )
drbd2: receiver (re)started
drbd2: conn( Unconnected -> WFConnection )
drbd2: conn( WFConnection -> WFReportParams )
drbd2: Handshake successful: DRBD Network Protocol version 85
drbd2: No resync, but bits in bitmap!
drbd2: peer( Unknown -> Secondary ) conn( WFReportParams -> Connected )
pdsk( DUnknown -> Inconsistent )
drbd2: Writing meta data super block now.
drbd2: aftr_isp( 0 -> 1 )
drbd2: No resync, but bits in bitmap!
drbd2: peer_isp( 0 -> 1 )
drbd2: No resync, but bits in bitmap!
drbd2: peer_isp( 1 -> 0 )
drbd2: aftr_isp( 1 -> 0 )

-----Original Message-----
From: drbd-dev-bounces@linbit.com [mailto:drbd-dev-bounces@linbit.com]
On Behalf Of Philipp Reisner
Sent: Monday, December 04, 2006 5:29 AM
To: drbd-dev@linbit.com
Subject: Re: [Drbd-dev] DRBD8: rr-conflict violently breaks sync states.

Am Freitag, 1. Dezember 2006 23:10 schrieb Montrose, Ernest:
> If "rr-conflict vilently;" is present in /etc/drbd.conf then the drbd
> volumes will not sync completely. Some of them ends up in :
> cs: Connected:St: secondary/Secondary:ds: Inconsistent/Inconsistent
>
> These states are on both nodes.
>
> It seems like this rr-conflict violently is not fully implemented.


Hi Ernest,

Actually it is. Could you grep in the kernel-logfile for all messages of
the devices that ended up in that state. Preferrable from both nodes.

Thanks!

-phil
-- 
: Dipl-Ing Philipp Reisner                      Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH          Fax +43-1-8178292-82 :
: Vivenotgasse 48, 1120 Vienna, Austria        http://www.linbit.com :
_______________________________________________
drbd-dev mailing list
drbd-dev@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-dev
_______________________________________________
drbd-dev mailing list
drbd-dev@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-dev

^ permalink raw reply	[flat|nested] 5+ messages in thread
* RE: [Drbd-dev] DRBD8: rr-conflict violently breaks sync states.
@ 2006-12-05 13:53 Montrose, Ernest
  0 siblings, 0 replies; 5+ messages in thread
From: Montrose, Ernest @ 2006-12-05 13:53 UTC (permalink / raw)
  To: Philipp Reisner, drbd-dev

Phil,
This issue is resolved!!!It was a problem in the way we install and the
fact
That the drbd user tools have changed. Sorry about the false alarm :)

EM--
-----Original Message-----
From: drbd-dev-bounces@linbit.com [mailto:drbd-dev-bounces@linbit.com]
On Behalf Of Philipp Reisner
Sent: Monday, December 04, 2006 5:29 AM
To: drbd-dev@linbit.com
Subject: Re: [Drbd-dev] DRBD8: rr-conflict violently breaks sync states.

Am Freitag, 1. Dezember 2006 23:10 schrieb Montrose, Ernest:
> If "rr-conflict vilently;" is present in /etc/drbd.conf then the drbd
> volumes will not sync completely. Some of them ends up in :
> cs: Connected:St: secondary/Secondary:ds: Inconsistent/Inconsistent
>
> These states are on both nodes.
>
> It seems like this rr-conflict violently is not fully implemented.


Hi Ernest,

Actually it is. Could you grep in the kernel-logfile for all messages of
the devices that ended up in that state. Preferrable from both nodes.

Thanks!

-phil
-- 
: Dipl-Ing Philipp Reisner                      Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH          Fax +43-1-8178292-82 :
: Vivenotgasse 48, 1120 Vienna, Austria        http://www.linbit.com :
_______________________________________________
drbd-dev mailing list
drbd-dev@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-dev

^ permalink raw reply	[flat|nested] 5+ messages in thread
end of thread, other threads:[~2006-12-05 13:53 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-12-01 22:10 [Drbd-dev] DRBD8: rr-conflict violently breaks sync states Montrose, Ernest
2006-12-04 10:28 ` Philipp Reisner
  -- strict thread matches above, loose matches on Subject: below --
2006-12-04 13:52 Montrose, Ernest
2006-12-04 15:08 Montrose, Ernest
2006-12-05 13:53 Montrose, Ernest

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox