From: Huamin Chen <hchen@redhat.com>
To: ceph-devel@vger.kernel.org
Subject: rbd lock list command failure
Date: Wed, 9 Sep 2015 12:26:47 -0400 (EDT) [thread overview]
Message-ID: <1133197671.21438012.1441816007901.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <638484117.21434546.1441815449448.JavaMail.zimbra@redhat.com>
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
rbd version:
[root@host server]# docker run -ti ceph/base ceph -v
ceph version 0.94.2 (5fb85614ca8f354284c713a2f9c610860720bbf3)
ceph server version:
# ceph -v
ceph version 0.80.9 (b5a67f0e1d15385bc0d60a6da6e7fc810bde6047)
next parent reply other threads:[~2015-09-09 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <638484117.21434546.1441815449448.JavaMail.zimbra@redhat.com>
2015-09-09 16:26 ` Huamin Chen [this message]
2015-09-14 22:35 ` rbd lock list command failure Josh Durgin
2015-09-15 13:10 ` Huamin Chen
2015-09-15 15:59 ` Josh Durgin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1133197671.21438012.1441816007901.JavaMail.zimbra@redhat.com \
--to=hchen@redhat.com \
--cc=ceph-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.