I think it's more helpful to put returned value in:
# ./src/krbd.cc
530 cerr << "rbd: sysfs write failed" << std::endl;
like:
530 cerr << "rbd: sysfs write failed (" << r << ")" << std::endl;
So that we exactly know what **write** complains about.
Because **write** has some return values in case of error.
What do you think?
Shinobu
----- Original Message -----
From: "Jeff Epstein" <jeff.epstein@xxxxxxxxxxxxxxxx>
To: "Jan Schermer" <jan@xxxxxxxxxxx>
Cc: ceph-users@xxxxxxxxxxxxxx
Sent: Saturday, September 26, 2015 2:44:00 AM
Subject: Re: [ceph-users] occasional failure to unmap rbd
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 the rbd's mounted block device name, of course, which
didn't turn up anything. Just now I tried searching for the minor device
number, but I didn't see anything obviously useful. lsof usually just
shows processes, so if the the device is being held by a kernel module
or inaccurate refcount, lsof wouldn't help.
Jeff
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
--
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
