On 09/25/2015 02:28 PM, Jan Schermer wrote:
What about /sys/block/krbdX/holders? Nothing in there?
There is no /sys/block/krbd450, but there is /sys/block/rbd450. In our
case, /sys/block/rbd450/holders is empty.
Jeff
___
ceph-users mailing list
ceph
On Fri, Sep 25, 2015 at 7:41 PM, Jeff Epstein
wrote:
> On 09/25/2015 12:38 PM, Ilya Dryomov wrote:
>>
>> On Fri, Sep 25, 2015 at 7:17 PM, Jeff Epstein
>> wrote:
>>>
>>> We occasionally have a situation where we are unable to unmap an rbd.
>>> This
>>> occurs intermittently, with no obvious cause.
What about /sys/block/krbdX/holders? Nothing in there?
Jan
> On 25 Sep 2015, at 19:44, Jeff Epstein wrote:
>
> On 09/25/2015 12:53 PM, Jan Schermer wrote:
>> What are you looking for in lsof? Did you try looking for the major/minor
>> number of the rbd device?
>> Things that could hold the dev
On 09/25/2015 12:53 PM, Jan Schermer wrote:
What are you looking for in lsof? Did you try looking for the major/minor
number of the rbd device?
Things that could hold the device are devicemapper, lvm, swraid and possibly
many more, not sure if all that shows in lsof output...
I searched for th
What are you looking for in lsof? Did you try looking for the major/minor
number of the rbd device?
Things that could hold the device are devicemapper, lvm, swraid and possibly
many more, not sure if all that shows in lsof output...
Jan
> On 25 Sep 2015, at 18:41, Jeff Epstein wrote:
>
> On 0
On 09/25/2015 12:38 PM, Ilya Dryomov wrote:
On Fri, Sep 25, 2015 at 7:17 PM, Jeff Epstein
wrote:
We occasionally have a situation where we are unable to unmap an rbd. This
occurs intermittently, with no obvious cause. For the most part, rbds can be
unmapped fine, but sometimes we get this:
# r
On Fri, Sep 25, 2015 at 7:17 PM, Jeff Epstein
wrote:
> We occasionally have a situation where we are unable to unmap an rbd. This
> occurs intermittently, with no obvious cause. For the most part, rbds can be
> unmapped fine, but sometimes we get this:
>
> # rbd unmap /dev/rbd450
> rbd: sysfs writ
We occasionally have a situation where we are unable to unmap an rbd.
This occurs intermittently, with no obvious cause. For the most part,
rbds can be unmapped fine, but sometimes we get this:
# rbd unmap /dev/rbd450
rbd: sysfs write failed
rbd: unmap failed: (16) Device or resource busy
Thin
