Re: Force unmap of RBD image

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Sep 10, 2018 at 10:46 AM Martin Palma <martin@xxxxxxxx> wrote:
>
> We are trying to unmap an rbd image form a host for deletion and
> hitting the following error:
>
> rbd: sysfs write failed
> rbd: unmap failed: (16) Device or resource busy
>
> We used commands like "lsof" and "fuser" but nothing is reported to
> use the device. Also checked for watcher with "rados -p pool
> listwatchers image.rbd" but there aren't any listed.

The device is still open by someone.  Check for LVM volumes, multipath,
loop devices etc.  None of those typically show up in lsof.

>
> By investigating `/sys/kernel/debug/ceph/<cluster-id>/osdc` we get:
>
> 160460241    osd150    19.b2af34    image.rbd
> 231954'1271503593144320    watch

Which kernel is that?

>
> Our goal is to unmap the image for deletion so if the unmap process
> should destroy the image is for us OK.
>
> Any help/suggestions?

On newer kernels you could do "rbd umap -o force <device>", but it
looks like you are running an older kernel.

Thanks,

                Ilya
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux