Hey guys,<div><br></div><div>I ran into an odd issue with LVM and the wiping the drbd meta data from a logical volume. Here is what my wipe md command looks like, this is all done via a script:</div><div><br></div><div>drbdmeta --force num v08 /dev/vg0/vol100 internal wipe-md</div>
<div><br></div><div>Which succeeds, but then when the script performs a back to back lvremove:</div><div><br></div><div>lvremove -f /dev/vg0/vol100</div><div><br></div><div>I get this error a few times, but after a few retries of lvremove succeeds:</div>
<div><br></div><div>Can't remove open logical volume "vol100"</div><div><br></div><div>So I'm thinking even after the drbdmeta command returns, somehow there is still a file descriptor open on the logical volume. Could it be udev doing something? In my situation, when I remove the wipe-md command before the lvremove, the issue goes away completely.</div>
<div><br></div><div>In a related question, is it necessary at all to wipe the drbd meta data? I did it to avoid those 'strange bm offset' messages, but could it cause problems if I just ignore wiping it?</div><div>
<br></div><div>Thanks,</div><div><br></div><div>Chris</div><div><br></div>