13.03.2013 20:37, Andreas Pflug wrote: > Am 13.03.13 17:53, schrieb Vladislav Bogdanov: >> >> #metadata/lv_manip.c:4137 Clearing start of logical volume "testvol2" >> #device/dev-cache.c:599 /dev/san2/testvol2: stat failed: No such >> file or directory >> #metadata/lv_manip.c:4140 /dev/san2/testvol2: not found: device not >> cleared >> #metadata/lv_manip.c:4620 Aborting. Failed to wipe start of new LV. >> Yep, I know about this, I reworked that patch a lot, and now it does >> every thing I wanted without regressions. >> I will try to post updated version in the next few days when I manage to >> apply it to a git tree. > > Is there a way to find out if a LV is locked exclusively? lvs displaying > -e-- instead of -a-- would be nice. Seems not even lvdisplay knows about > exclusive locking. That would break other tools which rely on their output. F.e. cluster resource agents of libvirt (yes, it runs lvm tools rather then using API, which is not yet complete btw). As I also need to obtain this information, I think about writing simple tool (f.e. clvm_tool) which would display needed info. As a workaround you can run lvchange -aly without force parameter. If it succeeds, the volume is locked in a shared mode, otherwise it is locked exclusively. > > Regards, > Andreas _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
