On Wed, Jul 5, 2017 at 7:55 PM, Stanislav Kopp <staskopp@xxxxxxxxx> wrote: > Hello, > > I have problem that sometimes I can't unmap rbd device, I get "sysfs > write failed rbd: unmap failed: (16) Device or resource busy", there > is no open files and "holders" directory is empty. I saw on the > mailling list that you can "force" unmapping the device, but I cant > find how does it work. "man rbd" only mentions "force" as "KERNEL RBD > (KRBD) OPTION", but "modinfo rbd" doesn't show this option. Did I miss > something? Forcing unmap on an open device is not a good idea. I'd suggest looking into what's holding the device and fixing that instead. Did you see http://tracker.ceph.com/issues/12763? > > As client where rbd is mapped I use Debian stretch with kernel 4.9, > ceph cluster is on version 11.2. rbd unmap -o force $DEV Thanks, Ilya _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |