On 09/09/2015 09:26 AM, Huamin Chen wrote:
Hi
Running "rbd lock list" inside a Docker container yields mixed results.
Sometimes I can get the right results but most times I just get errors.
A good run is like this:
[root@host server]# docker run --privileged --net=host -v /dev:/dev -v
/sys:/sys ceph/base rbd lock list foo --pool kube --id kube -m host:6789
--key=AQAMgXhVwBCeDhAA9nlPaFyfUSatGD4drFWDvQ==
2015-09-09 16:11:16.812858 7f3337ff5840 -1 did not load config file, using
default settings.
There is 1 exclusive lock on this image.
Locker ID Address
client.4333 kubelet_lock_magic_host 10.16.154.78:0/1000001
Same commands but with error:
[root@host server]# docker run --privileged --net=host -v /dev:/dev -v
/sys:/sys ceph/base rbd lock list foo --pool kube --id kube -m host:6789
--key=AQAMgXhVwBCeDhAA9nlPaFyfUSatGD4drFWDvQ==
2015-09-09 16:11:30.430345 7f4159766840 -1 did not load config file, using
default settings.
2015-09-09 16:11:30.464193 7f4159766840 -1 librbd::ImageCtx: error finding
header: (108) Cannot send after transport endpoint shutdown
rbd: error opening image foo: (108) Cannot send after transport endpoint
shutdown
Are you using blacklisting? That is the error that a blacklisted client
gets from rados.
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
