Two partitions nodes is same size? Aparentely not.<br><br><br><br><br><br><div class="gmail_quote">On Thu, Jul 22, 2010 at 6:01 AM, putcha narayana <span dir="ltr"><<a href="mailto:putcha_laks@hotmail.com">putcha_laks@hotmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<font color="#ff0000">drbd0: Peer sets u_size to 9380 sectors<br>drbd0: The peer's disk size is too small!<br>drbd0: conn( WFReportParams -> Disconnecting )<br>drbd0: error receiving ReportSizes, l: 32!<br></font> <br>
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? <br>
Is there an easy way to resolve this issue?<br>
<br>
Complete output of dmesg:<br><a href="mailto:root@hapWibbSc2" target="_blank"><font color="#0068cf">Sc2</font></a>:~# dmesg |grep drbd<br>drbd: initialised. Version: 8.0.6 (api:86/proto:86)<br>drbd: SVN Revision: 3048 build by <a href="mailto:phil@mescal" target="_blank"><font color="#0068cf">phil@mescal</font></a>, 2007-09-03 10:39:27<br>
drbd: registered as block device major 147<br>drbd: minor_table @ 0xae365f60<br>drbd0: disk( Diskless -> Attaching )<br>drbd0: No usable activity log found.<br>drbd0: max_segment_size ( = BIO size ) = 32768<br>drbd0: drbd_bm_resize called with capacity == 18760<br>
drbd0: resync bitmap: bits=2345 words=74<br>drbd0: size = 9380 KB (9380 KB)<br>drbd0: reading of bitmap took 0 jiffies<br>drbd0: recounting of set bits took additional 0 jiffies<br>drbd0: 0 KB marked out-of-sync by on disk bit-map.<br>
drbd0: disk( Attaching -> UpToDate )<br>drbd0: Writing meta data super block now.<br>drbd0: conn( StandAlone -> Unconnected )<br>drbd0: receiver (re)started<br>drbd0: conn( Unconnected -> WFConnection )<br>drbd0: conn( WFConnection -> WFReportParams )<br>
drbd0: Handshake successful: DRBD Network Protocol version 86<br>drbd0: Considerable difference in lower level device sizes: 32176s vs. 18848s<br>drbd0: peer( Unknown -> Primary ) conn( WFReportParams -> WFBitMapT ) pdsk( DUnknown -> UpToDate )<br>
drbd0: Writing meta data super block now.<br>drbd0: conn( WFBitMapT -> WFSyncUUID )<br>drbd0: conn( WFSyncUUID -> SyncTarget ) disk( UpToDate -> Inconsistent )<br>drbd0: Began resync as SyncTarget (will sync 12 KB [3 bits set]).<br>
drbd0: Writing meta data super block now.<br>drbd0: Resync done (total 1 sec; paused 0 sec; 12 K/sec)<br>drbd0: conn( SyncTarget -> Connected ) disk( Inconsistent -> UpToDate )<br>drbd0: Writing meta data super block now.<br>
drbd0: peer( Primary -> Unknown ) conn( Connected -> Disconnecting ) pdsk( UpToDate -> DUnknown )<br>drbd0: short read expecting header on sock: r=-512<br>drbd0: asender terminated<br>drbd0: tl_clear()<br>drbd0: Connection closed<br>
drbd0: Writing meta data super block now.<br>drbd0: conn( Disconnecting -> StandAlone )<br>drbd0: receiver terminated<br>drbd0: disk( UpToDate -> Diskless )<br>drbd0: drbd_bm_resize called with capacity == 0<br>drbd0: worker terminated<br>
drbd: module cleanup done.<br>drbd: initialised. Version: 8.0.16 (api:86/proto:86)<br>drbd: GIT-hash: d30881451c988619e243d6294a899139eed1183d build by <a href="mailto:a22852@isdmldlinux" target="_blank"><font color="#0068cf">a22852@isdmldlinux</font></a>, 2010-05-24 04:23:26<br>
drbd: registered as block device major 147<br>drbd: minor_table @ 0xac679760<br>drbd0: disk( Diskless -> Attaching )<br>drbd0: Starting worker thread (from cqueue/0 [576])<br>drbd0: No usable activity log found.<br>drbd0: max_segment_size ( = BIO size ) = 32768<br>
drbd0: drbd_bm_resize called with capacity == 18760<br>drbd0: resync bitmap: bits=2345 words=74<br>drbd0: size = 9380 KB (9380 KB)<br>drbd0: recounting of set bits took additional 0 jiffies<br>drbd0: 0 KB (0 bits) marked out-of-sync by on disk bit-map.<br>
drbd0: disk( Attaching -> UpToDate )<br>drbd0: Barriers not supported on meta data device - disabling<br>drbd0: conn( StandAlone -> Unconnected )<br>drbd0: Starting receiver thread (from drbd0_worker [2348])<br>drbd0: receiver (re)started<br>
drbd0: conn( Unconnected -> WFConnection )<br>drbd0: Handshake successful: DRBD Network Protocol version 86<br>drbd0: conn( WFConnection -> WFReportParams )<br>drbd0: Starting asender thread (from drbd0_receiver [2353])<br>
drbd0: Considerable difference in lower level device sizes: 32176s vs. 18768s<br>drbd0: Considerable difference in user requested size: 9380s vs. 18760s<br>drbd0: Peer sets u_size to 9380 sectors<br>drbd0: The peer's disk size is too small!<br>
drbd0: conn( WFReportParams -> Disconnecting )<br>drbd0: error receiving ReportSizes, l: 32!<br>drbd0: asender terminated<br>drbd0: Terminating asender thread<br>drbd0: Connection closed<br>drbd0: conn( Disconnecting -> StandAlone )<br>
drbd0: receiver terminated<br>drbd0: Terminating receiver thread<br><br>
<br><br>PUTCHA LAKSHMINARAYANA. LAK <br><br><br><br> <br>
<hr>
From: <a href="mailto:putcha_laks@hotmail.com" target="_blank">putcha_laks@hotmail.com</a><br>To: <a href="mailto:drbd-user@lists.linbit.com" target="_blank">drbd-user@lists.linbit.com</a><br>Subject: Upgrade DRBD-8.0.6 to DRBD-8.0.16<br>
Date: Wed, 21 Jul 2010 09:00:51 +0000<br><br>
Hi,<br> <br>Our current system is running DRBD-8.0.6 on 2 boards, One of the baords is active and the other board is standby.<br>DRBD is configured with meta-disk set as internal, port 7789, protocol C, size 9380. Excerpts attached at the end.<br>
<br>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.<br> <br>Things modified to match DRBD-8.0.16:<br>In drbd.conf file size is modified as "size 9380K"<br>
All other entries are kept same as in DRBD-8.0.6<br> <br>Issues:<br>When drbd is started on standby drbdstatus shows <br>0: cs:WFConnection st:Secondary/Unknown ds:UpToDate/DUnknown C r---<br> <br>And Primary does not detect DRBD on standby board.<br>
0: cs:WFConnection st:Primary/Unknown ds:UpToDate/DUnknown C r---<br> <br>Questions:<br>1. Is DRBD-8.0.16 backward compatible with DRBD-8.0.6?<br>2. Why there is no communication between DRBD-8.0.6 and DRBD-8.0.16?<br>3. Can any one list all the changes one must do to upgrade DRBD version on a redundant setup (standby first and then active)?<br>
<br>Excerpts from drbd.conf of DRBD8.0.6:<br>disk {<br> on-io-error detach;<br> size 9380;<br>}<br> <br> on Sc1 {<br> device /dev/drbd0;<br> disk /dev/tffsb4;<br> address <a href="http://10.19.17.1:7789" target="_blank">10.19.17.1:7789</a>;<br>
meta-disk internal;<br> }<br> on Sc2 {<br> device /dev/drbd0;<br> disk /dev/tffsb4;<br> address <a href="http://10.19.18.1:7789" target="_blank">10.19.18.1:7789</a>;<br> meta-disk internal;<br>
}<br><br>Please do the needful,<br><br>Thanks and Regards,<br>LAK <br><div class="hm"><br><br><br><br>
<hr>
The dark side of terrorists revealed in MSN Internal Security <a href="http://news.in.msn.com/internalsecurity/" target="_blank">Get it now.</a> <br><hr>Manage your finance and manage money through MSN Money Special <a href="http://news.in.msn.com/moneyspecial/" target="_blank">Drag n' drop</a></div>
</div>
<br>_______________________________________________<br>
drbd-user mailing list<br>
<a href="mailto:drbd-user@lists.linbit.com">drbd-user@lists.linbit.com</a><br>
<a href="http://lists.linbit.com/mailman/listinfo/drbd-user" target="_blank">http://lists.linbit.com/mailman/listinfo/drbd-user</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>---------------------------------------------------------<br> .,p **"*=b.<br> ?P" .__ ` *b <br> |P .d?' `&, 9| Fábio PIres de Oliveira<br>
M: |} .~^ H' Business Solutions<br> & ` # ?_.)' CIO - SYSTEMS <br> `H. Linux User: 414078<br> `#? <br> ^|~<br>