[DRBD-user] Problem with create-md

Rene Mayrhofer rene.mayrhofer at gibraltar.at
Thu Aug 23 19:07:50 CEST 2007

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


Hi Lars,

Thanks for your quick answer!

On Donnerstag 23 August 2007, Lars Ellenberg wrote:
> configure for "flexible-internal".
> for drbd 0.7-style fixed size 128MB meta data, 100MB backend is
> obviously too small :)
Aha - so the minimum size for a drbd8 volume with internal meta-data is 128MB? 
That's a no-issue, I can just increase it.

I have now resized all the 100MB LVs to 128MB and drbdadm create-md worked:

root at jupiter1 ~]# /etc/init.d/drbd reload
Reloading DRBD configurationFailure: (119) No valid meta-data signature found.

        ==> Use 'drbdadm create-md res' to initialize meta-data area. <==

Command '/sbin/drbdsetup /dev/drbd19 
disk /dev/mapper/xendomains-swap_license /dev/mapper/xendomains-swap_license 
internal --set-defaults --create-device --on-io-error=detach' terminated with 
exit code 10
.
[root at jupiter1 ~]# drbdadm create-md xenswap-license
v08 Magic number not found
v07 Magic number not found
About to create a new drbd meta data block
on /dev/mapper/xendomains-swap_license.

 ==> This might destroy existing data! <==

Do you want to proceed?
[need to type 'yes' to confirm] yes

Creating meta data...
initialising activity log
NOT initialized bitmap (4 KB)
New drbd meta data block sucessfully created.
[root at jupiter1 ~]# drbdadm create-md xenswap-ns1
v08 Magic number not found
v07 Magic number not found
About to create a new drbd meta data block
on /dev/mapper/xendomains-swap_ns1.

 ==> This might destroy existing data! <==

Do you want to proceed?
[need to type 'yes' to confirm] yes

Creating meta data...
initialising activity log
NOT initialized bitmap (4 KB)
New drbd meta data block sucessfully created.
[root at jupiter1 ~]# drbdadm create-md xenswap-ns2
v08 Magic number not found
v07 Magic number not found
About to create a new drbd meta data block
on /dev/mapper/xendomains-swap_ns2.

 ==> This might destroy existing data! <==

Do you want to proceed?
[need to type 'yes' to confirm] yes

Creating meta data...
initialising activity log
NOT initialized bitmap (4 KB)
New drbd meta data block sucessfully created.
[root at jupiter1 ~]# drbdadm create-md xenswap-tunnel1
v08 Magic number not found
v07 Magic number not found
About to create a new drbd meta data block
on /dev/mapper/xendomains-swap_tunnel1.

 ==> This might destroy existing data! <==

Do you want to proceed?
[need to type 'yes' to confirm] yes

Creating meta data...
initialising activity log
NOT initialized bitmap (4 KB)
New drbd meta data block sucessfully created.
[root at jupiter1 ~]# /etc/init.d/drbd reload
Reloading DRBD configurationFailure: (119) No valid meta-data signature found.

        ==> Use 'drbdadm create-md res' to initialize meta-data area. <==

Command '/sbin/drbdsetup /dev/drbd11 
disk /dev/mapper/xendomains-swap_web1 /dev/mapper/xendomains-swap_web1 
internal --set-defaults --create-device --on-io-error=detach' terminated with 
exit code 10
.
[root at jupiter1 ~]# drbdadm create-md xenswap-web1
v08 Magic number not found
v07 Magic number not found
About to create a new drbd meta data block
on /dev/mapper/xendomains-swap_web1.

 ==> This might destroy existing data! <==

Do you want to proceed?
[need to type 'yes' to confirm] yes

Creating meta data...
initialising activity log
NOT initialized bitmap (12 KB)
New drbd meta data block sucessfully created.
[root at jupiter1 ~]# /etc/init.d/drbd reload
Reloading DRBD configuration jupiter1 kernel: Oops: 0003 [#1]
 jupiter1 kernel: SMP
 jupiter1 kernel: CPU:    1
 jupiter1 kernel: EIP is at disk_conf_to_tags+0x3f/0xe3 [drbd]
 jupiter1 kernel: eax: 0065736e   ebx: 00000000   ecx: 0016dbe7   edx: 
c57c9cd8
 jupiter1 kernel: esi: c586a0b0   edi: ca8c6000   ebp: cc380424   esp: 
e257df24
 jupiter1 kernel: ds: 007b   es: 007b   ss: 0069
 jupiter1 kernel: Process cqueue/1 (pid: 3719, ti=e257c000 task=e2c89000 
task.ti=e257c000)
 jupiter1 kernel: Stack: 00000000 ca825c30 e710d89c c10a7e80 00000000 e1e04c00 
ca825c20 ca825c14
 jupiter1 kernel: e9577de9 ca825c00 cc380410 e9589b80 e9578069 e1e04c00 
e1cf6268 e1cf6210
 jupiter1 kernel: e6599f00 00000000 e94d40a2 e1cf620c c0128960 e94d4099 
e1cf6268 e6599f14
 jupiter1 kernel: Call Trace:
 jupiter1 kernel: Code: 8b 1a 66 c7 41 0c 03 e0 89 71 08 8d 72 08 89 59 04 8b 
42 28 66 89 41 0e 8b 42 28 83 c1 10 89 4c 24 04 8b 7c 24 04 89 c1 c1 e9 02 
<f3> a5 89 c1 83 e1 03 74 02 f3 a4 8b 44 24 04 8d 72 2c 03 42 28
 jupiter1 kernel: EIP: [<e95761ae>] disk_conf_to_tags+0x3f/0xe3 [drbd] SS:ESP 
0069:e257df24

But then it went all wrong... :(

Any ideas?

best regards,
Rene


-- 
-------------------------------------------------
Gibraltar firewall       http://www.gibraltar.at/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20070823/728b36ea/attachment.pgp>


More information about the drbd-user mailing list