Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On 3/7/12 11:13 PM, Jose Ildefonso Camargo Tolosa wrote: > Ok, direct question here: why do you want to downgrade? (I considered > a downgrade once, but then was able to fix the issues I was having, > and just stayed with a patched 8.4.1) It was suggested because of a problem I had: <http://www.gossamer-threads.com/lists/linuxha/users/78469> The actual issue turned out to be how I configured RRP in corosync. However, given the general advice "stick to 8.3.12 for production systems" I see on this list, I did not upgrade back to 8.4.1 after I fixed the problem. > On Tue, Feb 28, 2012 at 7:02 PM, William Seligman > <seligman at nevis.columbia.edu> wrote: >> Is there any way of downgrading 8.4.1 to 8.3.12 without erasing the drbd >> partition? When I try to start drbd 8.3.12 on a 8.4.1 partition, I get: >> >> >> # service drbd start >> Starting DRBD resources: [ >> admin >> no suitable meta data found :( >> Command '/sbin/drbdmeta 0 v08 /dev/md2 internal check-resize' terminated with >> exit code 255 >> drbdadm check-resize admin: exited with code 255 >> d(admin) 0: Failure: (119) No valid meta-data signature found. >> >> ==> Use 'drbdadm create-md res' to initialize meta-data area.<== >> >> >> [admin] cmd /sbin/drbdsetup 0 disk /dev/md2 /dev/md2 internal --set-defaults >> --create-device --fencing=resource-and-stonith failed - continuing! >> >> s(admin) n(admin) ]. >> >> >> >> >> OK, but when I try the suggested command: >> >> # drbdadm create-md admin >> pvs stderr: /dev/md2: Skipping (regex) >> pvs stderr: Failed to read physical volume "/dev/md2" >> pvs stderr: Unlocking /var/lock/lvm/P_global >> pvs stderr: _undo_flock /var/lock/lvm/P_global >> >> md_offset 2873200996352 >> al_offset 2873200963584 >> bm_offset 2873113276416 >> >> Found LVM2 physical volume signature >> 2805774684 kB left usable by current configuration >> Could not determine the size of the actually used data area. >> >> Device size would be truncated, which >> would corrupt data and result in >> 'access beyond end of device' errors. >> If you want me to do this, you need to zero out the first part >> of the device (destroy the content). >> You should be very sure that you mean it. >> Operation refused. >> >> Command 'drbdmeta 0 v08 /dev/md2 internal create-md' terminated with exit code 40 >> drbdadm create-md admin: exited with code 40 -- Bill Seligman | mailto://seligman@nevis.columbia.edu Nevis Labs, Columbia Univ | http://www.nevis.columbia.edu/~seligman/ PO Box 137 | Irvington NY 10533 USA | Phone: (914) 591-2823 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4497 bytes Desc: S/MIME Cryptographic Signature URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20120307/d98a1438/attachment.bin>