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

Mailing List Archive: DRBD: Users

Upgrade DRBD-8.0.6 to DRBD-8.0.16

 

 

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


putcha_laks at hotmail

Jul 21, 2010, 2:00 AM

Post #1 of 2 (376 views)
Permalink
Upgrade DRBD-8.0.6 to DRBD-8.0.16

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




_________________________________________________________________
See the news as it happens on MSN videos
http://video.in.msn.com/


putcha_laks at hotmail

Jul 23, 2010, 12:27 AM

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

I have removed the line size 9380 in drbd.conf of active SC and rebooted it.

After that when DRBD is brought up on Standby SC, Handshake was successful, but pdsk( DUnknown -> Diskless ).



Can some one help me resolving this issue?



Excerpts from drbd.conf:
disk {
on-io-error detach;
}

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;
}




Sc2:~# dmesg |grep drbd

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 @ 0xad8ad3e0

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 == 18768

drbd0: resync bitmap: bits=2346 words=74

drbd0: size = 9384 KB (9384 KB)

drbd0: recounting of set bits took additional 0 jiffies

drbd0: 9384 KB (2346 bits) marked out-of-sync by on disk bit-map.

drbd0: disk( Attaching -> Inconsistent )

drbd0: Barriers not supported on meta data device - disabling

drbd0: conn( StandAlone -> Unconnected )

drbd0: Starting receiver thread (from drbd0_worker [1581])

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 [1586])

drbd0: Considerable difference in lower level device sizes: 32176s vs. 18768s

drbd0: conn( WFReportParams -> Connected ) pdsk( DUnknown -> Diskless )



PUTCHA LAKSHMINARAYANA. LAK






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



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






Chin music and high voltage T20 action on MSN Sports Sign up now.
_________________________________________________________________
The world on four wheels in MSN Autos
http://autos.in.msn.com/

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.