[DRBD-user] 0.7 to 8.2 conversion

Michael Dodd mdodd at prweb.com
Thu Mar 25 21:42:57 CET 2010

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


Here's the uname -a output on our system(s):
 
 $ uname -a
Linux baker3.dmz.prweb.local 2.6.9-89.0.23.ELsmp #1 SMP Wed Mar 17
06:49:21 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
 
Our drbd.conf:
 
 $ cat /etc/drbd.conf
#
# drbd.conf example
#
#global { usage-count yes; }
#common { syncer { rate 1000M; } }
 
resource r0 {
        protocol C;
        net {
        #       on-disconnect reconnect;
                ping-int 7;
                connect-int 7;
        }
        disk { on-io-error detach; }
        syncer { rate 100M; }
        on baker2.dmz.prweb.local {
                device     /dev/drbd0;
                disk       /dev/sdb1;
                address    10.143.254.110:7789;
                meta-disk  /dev/vg00/lvMetaDisk[0];
        }
 
        on baker3.dmz.prweb.local {
                device    /dev/drbd0;
                disk      /dev/sdb1;
                address   10.143.254.111:7789;
                meta-disk /dev/vg00/lvMetaDisk[0];
        }
}
 
resource r1 {
        protocol C;
        net {
        #       on-disconnect reconnect;
                ping-int 7;
                connect-int 7;
        }
        disk { on-io-error detach; }
        syncer { rate 100M; }
        on baker2.dmz.prweb.local {
                device /dev/drbd1;
                disk /dev/sdb2;
                address 10.143.254.110:7788;
                meta-disk /dev/vg00/lvMetaDisk2[0];
        }
        on baker3.dmz.prweb.local {
                device /dev/drbd1;
                disk /dev/sdb2;
                address 10.143.254.111:7788;
                meta-disk /dev/vg00/lvMetaDisk2[0];
        }
}

New packages are installed without trouble, but when I run drbdadm
create-md r0 I get:
 
v08 Magic number not found
md_offset 0
al_offset 4096
bm_offset 36864
 
Found ext2 filesystem
This would corrupt existing data.
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 /dev/drbd1 v08 /dev/vg00/lvMetaDisk2 0 create-md'
terminated with exit code 40
drbdadm aborting
 
I can confirm that the data is synced correctly between our two nodes.  
 
My two questions:
 
1)  Did I do something wrong or do I have an otherwise broken
configuration?
 
2)  If I don't care about having to do a resync, can I just create a new
set of metadata, invalidate the metadata on the second node and let them
resync?
 
thanks in advance!
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20100325/22c110d8/attachment.htm>


More information about the drbd-user mailing list