> Currently it is not allowed to issue an evict op > (CEPH_OSD_OP_CACHE_EVICT) on an object which has watchers (e.g. the > rbd header). EBUSY is returned in this case. This leads to the the > flush-evict-all failure during removing a cache tier, something like > below: > > rbd_header.4fc06b8b4567 > failed to evict /rbd_header.4fc06b8b4567: (16) Device or resource busy > > My question is that do we actually need to do so? The object in the > base pool should have the watcher information as well after the flush. > Probably we could remove this 'watcher' check to make flush-evict-all > happy? > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > I opened a ticket [1] a couple of months ago to address this issue. [1] http://tracker.ceph.com/issues/14865 -- Jason Dillaman -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
