[DRBD-user] Migration metadata from 0.7.x to 8.x.x fail with "Magic number not found"
francis.souyri at apec.fr
Tue Nov 13 08:26:43 CET 2007
Lars, Phillip, Florian, do you have an idea why the 0.7.x find the
metadata magic number of the resource and the 8.2.x do not ?
Francis SOUYRI wrote:
> In attachment you have the drbd.conf for the 0.7.25 and 8.2.0.
> Best regards.
> Francis SOUYRI wrote:
>> I tried to upgrade a cluster with internal metadata from drbd 0.7.25
>> to drbd 8.2.0 with this procedure.
>> On one node (the packages are running on the other node).
>> * /etc/init.d/heartbeat
>> # stop heartbeat
>> * /etc/init.d/drbd
>> # stop drbd
>> * rpm -ev drbd-km-184.108.40.206_91.fc7-0.7.25-1
>> drbd-0.7.25-1 # remove drbd
>> * rpm -ivh drbd-km-220.127.116.11_91.fc7-8.2.0-3.i386.rpm
>> drbd-8.2.0-3.i386.rpm # install drbd 8.2.0
>> * cp -p /etc/drbd.conf.new
>> # install the drbd 8.2.0 config
>> * drbdadm create-md <resource
>> # migrate each resources
>> But the last command failed for 6 of the 7 resources (only drbd0
>> migrate) with the message:
>> ##### BEGIN
>> You are using the 'drbd-peer-outdater' as outdate-peer program.
>> If you use that mechanism the dopd heartbeat plugin program needs
>> to be able to call drbdsetup and drbdmeta with root privileges.
>> You need to fix this with these commands:
>> chgrp haclient /sbin/drbdmeta
>> chmod o-x /sbin/drbdmeta
>> chmod u+s /sbin/drbdmeta
>> v08 Magic number not found
>> v07 Magic number not found
>> About to create a new drbd meta data block
>> on /dev/vgroot/lv<resource name>.
>> ==> This might destroy existing data! <==
>> Do you want to proceed?
>> [need to type 'yes' to confirm]
>> ##### END
>> I tested with drbd 8.0.6 and I have the same problem, I do not test
>> the 8.2.1 or 8.0.7...
>> I hope my post is clearer, if not please do not hesitate to ask me
>> Best regards.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the drbd-user