[ovirt-users] Disk from FC storage not removed

[Nir Soffer]

On Thu, Jun 9, 2016 at 11:46 AM, Krzysztof Dajka <alteriks at gmail.com> wrote:
> Hi,
>
> Recently I tried to delete 1TB disk created on top ~3TB LUN from
> ovirtengine.
> Disk is preallocated and I backuped data to other disk so I could recreate
> it once again as thin volume. I couldn't remove this disk when it was
> attached to a VM. But once I detached it I could remove it permanently. The
> thing is it only disappeared from ovirtengine GUI.
>
> I've got 4 hosts with FC HBA attached to storage array and all of them are
> saying that this 1TB disk which should be gone is opened by all hosts
> simultaneously.
>
> [root at wrops1 BLUE ~]# lvdisplay -m
> /dev/e69d1c16-36d1-4375-aaee-69f5a5ce1616/ee53af81-820d-4916-b766-5236ca99daf8
>   --- Logical volume ---
>   LV Path
> /dev/e69d1c16-36d1-4375-aaee-69f5a5ce1616/ee53af81-820d-4916-b766-5236ca99daf8
>   LV Name                ee53af81-820d-4916-b766-5236ca99daf8
>   VG Name                e69d1c16-36d1-4375-aaee-69f5a5ce1616
>   LV UUID                sBdBRk-tNyZ-Rval-F4lw-ka6X-wOe8-AQenTb
>   LV Write Access        read/write
>   LV Creation host, time wrops1.blue, 2015-07-31 10:40:57 +0200
>   LV Status              available
>   # open                 1
>   LV Size                1.00 TiB
>   Current LE             8192
>   Segments               1
>   Allocation             inherit
>   Read ahead sectors     auto
>   - currently set to     8192
>   Block device           253:29
>
>   --- Segments ---
>   Logical extents 0 to 8191:
>     Type                linear
>     Physical volume     /dev/mapper/3600000e00d0000000024057200000000
>     Physical extents    8145 to 16336
>
> Deactivating LV doesn't work:
> [root at wrops1 BLUE ~]# lvchange -an
> /dev/e69d1c16-36d1-4375-aaee-69f5a5ce1616/ee53af81-820d-4916-b766-5236ca99daf8
>   Logical volume
> e69d1c16-36d1-4375-aaee-69f5a5ce1616/ee53af81-820d-4916-b766-5236ca99daf8 is
> used by another device.

Looks like your lv is used as a physical volume on another vg - probably
a vg created on a guest. Lvm and systemd are trying hard to discover
stuff on multipath devices and expose anything to the hypervisor.

Can you share the output of:

    ls -l /sys/block/$(basename $(readlink
/dev/e69d1c16-36d1-4375-aaee-69f5a5ce1616/ee53af81-820d-4916-b766-5236ca99daf8))/holders

And:

    pvscan --cache
    vgs -o pv_name,vg_name

Nir

> Removing from hypervisor doesn't work either.
> [root at wrops1 BLUE ~]# lvremove --force
> /dev/e69d1c16-36d1-4375-aaee-69f5a5ce1616/ee53af81-820d-4916-b766-5236ca99daf8
>   Logical volume
> e69d1c16-36d1-4375-aaee-69f5a5ce1616/ee53af81-820d-4916-b766-5236ca99daf8 is
> used by another device.
>
> I tried and rebooted one host and as soon as it booted the volume became
> opened once again. Lsof on all hosts doesn't give anything meaningful
> regarding this LV. As opposed to other LV which are used by qemu-kvm.
>
> Has anyone encountered similar problem? How can I remove this LV?
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>