Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Jul 29, 2011, at 3:41 AM, Junko IKEDA wrote: > Hi, > > I got it. > drbdadm wipe-md + create-md are needed. > > 0) start DRBD on 2 node, as Primary/Secnodary > > on Secondary; > 1) stop DRBD > # drbdadm down all > # service drbd stop > > 2) remove old DRBD > # rpm -e drbd-km-2.6.18_238.el5-8.3.11-1 drbd-pacemaker-8.3.11-1 > drbd-utils-8.3.11-1 > > 3) install new DRBD > # rpm -ihv drbd-utils-8.4.0-1.x86_64.rpm > drbd-km-2.6.18_238.el5-8.4.0-1.x86_64.rpm > drbd-pacemaker-8.4.0-1.x86_64.rpm > # chkconfig drbd off > > 4) create drbd.conf > # cp -p /etc/drbd.conf.rpmsave /etc/drbd.conf > > 5) refresh meta-data > # drbdadm wipe-md all > # drbdadm create-md all > > 6) start DRBD > # service drbd start > > # cat /proc/drbd > version: 8.4.0 (api:1/proto:86-100) > GIT-hash: 28753f559ab51b549d16bcf487fe625d5919c49c build by > root at bl460g1n13, 2011-07-25 13:46:08 > 0: cs:SyncTarget ro:Secondary/Primary ds:Inconsistent/UpToDate C > r----- > ns:0 nr:0 dw:0 dr:263296 al:0 bm:15 lo:22 pe:46 ua:0 ap:0 ep:1 > wo:b oos:9513840 > [>....................] sync'ed: 2.7% (9288/9540)M > finish: 0:03:41 speed: 42,900 (42,900) want: 40,960 K/sec > > # cat /proc/drbd > version: 8.4.0 (api:1/proto:86-100) > GIT-hash: 28753f559ab51b549d16bcf487fe625d5919c49c build by > root at bl460g1n13, 2011-07-25 13:46:08 > 0: cs:Connected ro:Secondary/Primary ds:UpToDate/UpToDate C r----- > ns:0 nr:0 dw:0 dr:9771248 al:0 bm:597 lo:0 pe:0 ua:0 ap:0 ep:1 > wo:b oos:0 > > Thanks, > Junko > Hi, I'm attempting a rolling update from 8.3.7 to 8.4.0 (hoping it solves my write performance problems), and running into the same 'drbd_md_sync_page_io(,...s,WRITE) failed!' problem. I have two nodes in primary/secondary with DRBD on top of LVM on top of md RAID10, and I get this on all of my DRBD resources. I'm attempting to update the secondary, the primary remained active and in-use on 8.3.7 during this. I had initially tried it without the metadata wipe/re-create -- after seeing this message I retried including those steps, but it didn't change anything. After the first attempt (without the wipe-md/create- md) I rolled back to 8.3.7 and when I re-attached my resources it appeared that the 8.4.0 upgrade attempt somehow nuked the metadata anyway, since 8.3.7 couldn't find a magic number, so I had to do a full re-sync. Now that I've made another attempt and gotten the same results, it looks like I'm going to have to do that again. Anyone else seen this, or have any other advice? Thanks, Zev