No subject


Mon Dec 9 19:55:22 CET 2019


<br>
# modinfo drbd<br>
filename:=C2=A0 =C2=A0 =C2=A0 =C2=A0/lib/modules/3.10.0-1062.18.1.el7.x86_6=
4/weak-updates/drbd90/drbd.ko<br>
alias:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 block-major-147-*<br>
license:=C2=A0 =C2=A0 =C2=A0 =C2=A0 GPL<br>
version:=C2=A0 =C2=A0 =C2=A0 =C2=A0 9.0.20-1<br>
<br>
Config is all default, ressource is like this:<br>
<br>
resource xxx {<br>
=C2=A0 device /dev/drbd0;<br>
=C2=A0 disk /dev/disk/by-id/nvme-Amazon_Elastic_Block_Store_volxxx;<br>
=C2=A0 meta-disk internal;<br>
=C2=A0 on node-1 {<br>
=C2=A0 =C2=A0 address <a href=3D"http://10.0.0.1:7788" rel=3D"noreferrer" t=
arget=3D"_blank">10.0.0.1:7788</a>;<br>
=C2=A0 }<br>
=C2=A0 on node-2 {<br>
=C2=A0 =C2=A0 address <a href=3D"http://10.0.0.2:7788" rel=3D"noreferrer" t=
arget=3D"_blank">10.0.0.2:7788</a>;<br>
=C2=A0 }<br>
}<br>
<br>
When trying to bring up the ressource, I get this error message:<br>
<br>
# drbdadm up xxx<br>
0: Failure: (119) No valid meta-data signature found.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =3D=3D&gt; Use &#39;drbdadm create-md res&#39; =
to initialize meta-data area. &lt;=3D=3D<br>
Command &#39;drbdsetup attach 0 /dev/disk/by-id/nvme-Amazon_Elastic_Block_S=
tore_volxxx /dev/disk/by-id/nvme-Amazon_Elastic_Block_Store_volxxx internal=
&#39; terminated with exit code 10<br>
<br>
=3D=3D=3D&gt; When doing as advised, I wonder about the following message:<=
br>
<br>
# drbdadm create-md xxx<br>
You want me to create a v09 style flexible-size internal meta data block.<b=
r>
There appears to be a v09 flexible-size internal meta data block<br>
already in place on /dev/disk/by-id/nvme-Amazon_Elastic_Block_Store_volxxx =
byte offset 64424505344<br>
<br>
=3D=3D=3D&gt; So it is saying there _is_ metadata already present. So why i=
s it not valid? Is this expected behavior when cloning a drbd physical disk=
 to another host? Is it safe to create new metadata in this case?<br>
<br>
Do you really want to overwrite the existing meta-data?<br>
[need to type &#39;yes&#39; to confirm] yes<br>
<br>
md_offset 64424505344<br>
al_offset 64424472576<br>
bm_offset 64422506496<br>
<br>
Found ext3 filesystem<br>
=C2=A0 =C2=A0 62912604 kB data area apparently used<br>
=C2=A0 =C2=A0 62912604 kB left usable by current configuration<br>
<br>
Even though it looks like this would place the new meta data into<br>
unused space, you still need to confirm, as this is only a guess.<br>
<br>
Do you want to proceed?<br>
[need to type &#39;yes&#39; to confirm] yes<br>
<br>
initializing activity log<br>
initializing bitmap (1920 KB) to all zero<br>
Writing meta data...<br>
New drbd meta data block successfully created.<br>
<br>
<br>
Thanks much &amp; regards<br>
Markus<br>
_______________________________________________<br>
Star us on GITHUB: <a href=3D"https://github.com/LINBIT" rel=3D"noreferrer"=
 target=3D"_blank">https://github.com/LINBIT</a><br>
drbd-user mailing list<br>
<a href=3D"mailto:drbd-user at lists.linbit.com" target=3D"_blank">drbd-user at l=
ists.linbit.com</a><br>
<a href=3D"https://lists.linbit.com/mailman/listinfo/drbd-user" rel=3D"nore=
ferrer" target=3D"_blank">https://lists.linbit.com/mailman/listinfo/drbd-us=
er</a><br>
</blockquote></div></div>

--000000000000dd80f905a41b9ccf--


More information about the drbd-user mailing list