Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: DRBD: Users

dmesg output for: Upgrade DRBD-8.0.6 to DRBD-8.0.16

 

 

DRBD users RSS feed   Index | Next | Previous | View Threaded


putcha_laks at hotmail

Jul 22, 2010, 2:01 AM

Post #1 of 2 (454 views)
Permalink
dmesg output for: Upgrade DRBD-8.0.6 to DRBD-8.0.16

drbd0: Peer sets u_size to 9380 sectors
drbd0: The peer's disk size is too small!
drbd0: conn( WFReportParams -> Disconnecting )
drbd0: error receiving ReportSizes, l: 32!

Can someone help in resolving this issue. If drbd8.0.6 and drbd-8.0.16 are compatible then why is drbd throwing the above error?

Is there an easy way to resolve this issue?



Complete output of dmesg:
Sc2:~# dmesg |grep drbd
drbd: initialised. Version: 8.0.6 (api:86/proto:86)
drbd: SVN Revision: 3048 build by phil [at] mesca, 2007-09-03 10:39:27
drbd: registered as block device major 147
drbd: minor_table @ 0xae365f60
drbd0: disk( Diskless -> Attaching )
drbd0: No usable activity log found.
drbd0: max_segment_size ( = BIO size ) = 32768
drbd0: drbd_bm_resize called with capacity == 18760
drbd0: resync bitmap: bits=2345 words=74
drbd0: size = 9380 KB (9380 KB)
drbd0: reading of bitmap took 0 jiffies
drbd0: recounting of set bits took additional 0 jiffies
drbd0: 0 KB marked out-of-sync by on disk bit-map.
drbd0: disk( Attaching -> UpToDate )
drbd0: Writing meta data super block now.
drbd0: conn( StandAlone -> Unconnected )
drbd0: receiver (re)started
drbd0: conn( Unconnected -> WFConnection )
drbd0: conn( WFConnection -> WFReportParams )
drbd0: Handshake successful: DRBD Network Protocol version 86
drbd0: Considerable difference in lower level device sizes: 32176s vs. 18848s
drbd0: peer( Unknown -> Primary ) conn( WFReportParams -> WFBitMapT ) pdsk( DUnknown -> UpToDate )
drbd0: Writing meta data super block now.
drbd0: conn( WFBitMapT -> WFSyncUUID )
drbd0: conn( WFSyncUUID -> SyncTarget ) disk( UpToDate -> Inconsistent )
drbd0: Began resync as SyncTarget (will sync 12 KB [3 bits set]).
drbd0: Writing meta data super block now.
drbd0: Resync done (total 1 sec; paused 0 sec; 12 K/sec)
drbd0: conn( SyncTarget -> Connected ) disk( Inconsistent -> UpToDate )
drbd0: Writing meta data super block now.
drbd0: peer( Primary -> Unknown ) conn( Connected -> Disconnecting ) pdsk( UpToDate -> DUnknown )
drbd0: short read expecting header on sock: r=-512
drbd0: asender terminated
drbd0: tl_clear()
drbd0: Connection closed
drbd0: Writing meta data super block now.
drbd0: conn( Disconnecting -> StandAlone )
drbd0: receiver terminated
drbd0: disk( UpToDate -> Diskless )
drbd0: drbd_bm_resize called with capacity == 0
drbd0: worker terminated
drbd: module cleanup done.
drbd: initialised. Version: 8.0.16 (api:86/proto:86)
drbd: GIT-hash: d30881451c988619e243d6294a899139eed1183d build by a22852 [at] isdmldlinu, 2010-05-24 04:23:26
drbd: registered as block device major 147
drbd: minor_table @ 0xac679760
drbd0: disk( Diskless -> Attaching )
drbd0: Starting worker thread (from cqueue/0 [576])
drbd0: No usable activity log found.
drbd0: max_segment_size ( = BIO size ) = 32768
drbd0: drbd_bm_resize called with capacity == 18760
drbd0: resync bitmap: bits=2345 words=74
drbd0: size = 9380 KB (9380 KB)
drbd0: recounting of set bits took additional 0 jiffies
drbd0: 0 KB (0 bits) marked out-of-sync by on disk bit-map.
drbd0: disk( Attaching -> UpToDate )
drbd0: Barriers not supported on meta data device - disabling
drbd0: conn( StandAlone -> Unconnected )
drbd0: Starting receiver thread (from drbd0_worker [2348])
drbd0: receiver (re)started
drbd0: conn( Unconnected -> WFConnection )
drbd0: Handshake successful: DRBD Network Protocol version 86
drbd0: conn( WFConnection -> WFReportParams )
drbd0: Starting asender thread (from drbd0_receiver [2353])
drbd0: Considerable difference in lower level device sizes: 32176s vs. 18768s
drbd0: Considerable difference in user requested size: 9380s vs. 18760s
drbd0: Peer sets u_size to 9380 sectors
drbd0: The peer's disk size is too small!
drbd0: conn( WFReportParams -> Disconnecting )
drbd0: error receiving ReportSizes, l: 32!
drbd0: asender terminated
drbd0: Terminating asender thread
drbd0: Connection closed
drbd0: conn( Disconnecting -> StandAlone )
drbd0: receiver terminated
drbd0: Terminating receiver thread




PUTCHA LAKSHMINARAYANA. LAK






From: putcha_laks [at] hotmail
To: drbd-user [at] lists
Subject: Upgrade DRBD-8.0.6 to DRBD-8.0.16
Date: Wed, 21 Jul 2010 09:00:51 +0000



Hi,

Our current system is running DRBD-8.0.6 on 2 boards, One of the baords is active and the other board is standby.
DRBD is configured with meta-disk set as internal, port 7789, protocol C, size 9380. Excerpts attached at the end.

To minimize outage by resetting both boards, we would like to upgrade and bring up standby board on DRBD-8.0.16 first. My attempts are not successful so far.

Things modified to match DRBD-8.0.16:
In drbd.conf file size is modified as "size 9380K"
All other entries are kept same as in DRBD-8.0.6

Issues:
When drbd is started on standby drbdstatus shows
0: cs:WFConnection st:Secondary/Unknown ds:UpToDate/DUnknown C r---

And Primary does not detect DRBD on standby board.
0: cs:WFConnection st:Primary/Unknown ds:UpToDate/DUnknown C r---

Questions:
1. Is DRBD-8.0.16 backward compatible with DRBD-8.0.6?
2. Why there is no communication between DRBD-8.0.6 and DRBD-8.0.16?
3. Can any one list all the changes one must do to upgrade DRBD version on a redundant setup (standby first and then active)?

Excerpts from drbd.conf of DRBD8.0.6:
disk {
on-io-error detach;
size 9380;
}

on Sc1 {
device /dev/drbd0;
disk /dev/tffsb4;
address 10.19.17.1:7789;
meta-disk internal;
}
on Sc2 {
device /dev/drbd0;
disk /dev/tffsb4;
address 10.19.18.1:7789;
meta-disk internal;
}

Please do the needful,

Thanks and Regards,
LAK






The dark side of terrorists revealed in MSN Internal Security Get it now.
_________________________________________________________________
Bollywood, beauties and the latest flicks on MSN entertainment
http://entertainment.in.msn.com/


fabio.pires at gmail

Jul 22, 2010, 12:07 PM

Post #2 of 2 (440 views)
Permalink
Re: dmesg output for: Upgrade DRBD-8.0.6 to DRBD-8.0.16 [In reply to]

Two partitions nodes is same size? Aparentely not.





On Thu, Jul 22, 2010 at 6:01 AM, putcha narayana <putcha_laks [at] hotmail>wrote:

> drbd0: Peer sets u_size to 9380 sectors
> drbd0: The peer's disk size is too small!
> drbd0: conn( WFReportParams -> Disconnecting )
> drbd0: error receiving ReportSizes, l: 32!
>
> Can someone help in resolving this issue. If drbd8.0.6 and drbd-8.0.16 are
> compatible then why is drbd throwing the above error?
> Is there an easy way to resolve this issue?
>
> Complete output of dmesg:
> Sc2 <root [at] hapWibbSc>:~# dmesg |grep drbd
> drbd: initialised. Version: 8.0.6 (api:86/proto:86)
> drbd: SVN Revision: 3048 build by phil [at] mesca, 2007-09-03 10:39:27
> drbd: registered as block device major 147
> drbd: minor_table @ 0xae365f60
> drbd0: disk( Diskless -> Attaching )
> drbd0: No usable activity log found.
> drbd0: max_segment_size ( = BIO size ) = 32768
> drbd0: drbd_bm_resize called with capacity == 18760
> drbd0: resync bitmap: bits=2345 words=74
> drbd0: size = 9380 KB (9380 KB)
> drbd0: reading of bitmap took 0 jiffies
> drbd0: recounting of set bits took additional 0 jiffies
> drbd0: 0 KB marked out-of-sync by on disk bit-map.
> drbd0: disk( Attaching -> UpToDate )
> drbd0: Writing meta data super block now.
> drbd0: conn( StandAlone -> Unconnected )
> drbd0: receiver (re)started
> drbd0: conn( Unconnected -> WFConnection )
> drbd0: conn( WFConnection -> WFReportParams )
> drbd0: Handshake successful: DRBD Network Protocol version 86
> drbd0: Considerable difference in lower level device sizes: 32176s vs.
> 18848s
> drbd0: peer( Unknown -> Primary ) conn( WFReportParams -> WFBitMapT ) pdsk(
> DUnknown -> UpToDate )
> drbd0: Writing meta data super block now.
> drbd0: conn( WFBitMapT -> WFSyncUUID )
> drbd0: conn( WFSyncUUID -> SyncTarget ) disk( UpToDate -> Inconsistent )
> drbd0: Began resync as SyncTarget (will sync 12 KB [3 bits set]).
> drbd0: Writing meta data super block now.
> drbd0: Resync done (total 1 sec; paused 0 sec; 12 K/sec)
> drbd0: conn( SyncTarget -> Connected ) disk( Inconsistent -> UpToDate )
> drbd0: Writing meta data super block now.
> drbd0: peer( Primary -> Unknown ) conn( Connected -> Disconnecting ) pdsk(
> UpToDate -> DUnknown )
> drbd0: short read expecting header on sock: r=-512
> drbd0: asender terminated
> drbd0: tl_clear()
> drbd0: Connection closed
> drbd0: Writing meta data super block now.
> drbd0: conn( Disconnecting -> StandAlone )
> drbd0: receiver terminated
> drbd0: disk( UpToDate -> Diskless )
> drbd0: drbd_bm_resize called with capacity == 0
> drbd0: worker terminated
> drbd: module cleanup done.
> drbd: initialised. Version: 8.0.16 (api:86/proto:86)
> drbd: GIT-hash: d30881451c988619e243d6294a899139eed1183d build by
> a22852 [at] isdmldlinu, 2010-05-24 04:23:26
> drbd: registered as block device major 147
> drbd: minor_table @ 0xac679760
> drbd0: disk( Diskless -> Attaching )
> drbd0: Starting worker thread (from cqueue/0 [576])
> drbd0: No usable activity log found.
> drbd0: max_segment_size ( = BIO size ) = 32768
> drbd0: drbd_bm_resize called with capacity == 18760
> drbd0: resync bitmap: bits=2345 words=74
> drbd0: size = 9380 KB (9380 KB)
> drbd0: recounting of set bits took additional 0 jiffies
> drbd0: 0 KB (0 bits) marked out-of-sync by on disk bit-map.
> drbd0: disk( Attaching -> UpToDate )
> drbd0: Barriers not supported on meta data device - disabling
> drbd0: conn( StandAlone -> Unconnected )
> drbd0: Starting receiver thread (from drbd0_worker [2348])
> drbd0: receiver (re)started
> drbd0: conn( Unconnected -> WFConnection )
> drbd0: Handshake successful: DRBD Network Protocol version 86
> drbd0: conn( WFConnection -> WFReportParams )
> drbd0: Starting asender thread (from drbd0_receiver [2353])
> drbd0: Considerable difference in lower level device sizes: 32176s vs.
> 18768s
> drbd0: Considerable difference in user requested size: 9380s vs. 18760s
> drbd0: Peer sets u_size to 9380 sectors
> drbd0: The peer's disk size is too small!
> drbd0: conn( WFReportParams -> Disconnecting )
> drbd0: error receiving ReportSizes, l: 32!
> drbd0: asender terminated
> drbd0: Terminating asender thread
> drbd0: Connection closed
> drbd0: conn( Disconnecting -> StandAlone )
> drbd0: receiver terminated
> drbd0: Terminating receiver thread
>
>
>
> PUTCHA LAKSHMINARAYANA. LAK
>
>
>
>
> ------------------------------
> From: putcha_laks [at] hotmail
> To: drbd-user [at] lists
> Subject: Upgrade DRBD-8.0.6 to DRBD-8.0.16
> Date: Wed, 21 Jul 2010 09:00:51 +0000
>
> Hi,
>
> Our current system is running DRBD-8.0.6 on 2 boards, One of the baords is
> active and the other board is standby.
> DRBD is configured with meta-disk set as internal, port 7789, protocol C,
> size 9380. Excerpts attached at the end.
>
> To minimize outage by resetting both boards, we would like to upgrade and
> bring up standby board on DRBD-8.0.16 first. My attempts are not successful
> so far.
>
> Things modified to match DRBD-8.0.16:
> In drbd.conf file size is modified as "size 9380K"
> All other entries are kept same as in DRBD-8.0.6
>
> Issues:
> When drbd is started on standby drbdstatus shows
> 0: cs:WFConnection st:Secondary/Unknown ds:UpToDate/DUnknown C r---
>
> And Primary does not detect DRBD on standby board.
> 0: cs:WFConnection st:Primary/Unknown ds:UpToDate/DUnknown C r---
>
> Questions:
> 1. Is DRBD-8.0.16 backward compatible with DRBD-8.0.6?
> 2. Why there is no communication between DRBD-8.0.6 and DRBD-8.0.16?
> 3. Can any one list all the changes one must do to upgrade DRBD version on
> a redundant setup (standby first and then active)?
>
> Excerpts from drbd.conf of DRBD8.0.6:
> disk {
> on-io-error detach;
> size 9380;
> }
>
> on Sc1 {
> device /dev/drbd0;
> disk /dev/tffsb4;
> address 10.19.17.1:7789;
> meta-disk internal;
> }
> on Sc2 {
> device /dev/drbd0;
> disk /dev/tffsb4;
> address 10.19.18.1:7789;
> meta-disk internal;
> }
>
> Please do the needful,
>
> Thanks and Regards,
> LAK
>
>
>
>
> ------------------------------
> The dark side of terrorists revealed in MSN Internal Security Get it now.<http://news.in.msn.com/internalsecurity/>
> ------------------------------
> Manage your finance and manage money through MSN Money Special Drag n'
> drop <http://news.in.msn.com/moneyspecial/>
>
> _______________________________________________
> drbd-user mailing list
> drbd-user [at] lists
> http://lists.linbit.com/mailman/listinfo/drbd-user
>
>


--
---------------------------------------------------------
.,p **"*=b.
?P" .__ ` *b
|P .d?' `&, 9| Fábio PIres de Oliveira
M: |} .~^ H' Business Solutions
& ` # ?_.)' CIO - SYSTEMS
`H. Linux User: 414078
`#?
^|~

DRBD users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.