-
Notifications
You must be signed in to change notification settings - Fork 255
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LockExclusive crash #20
Comments
This issue only affect ceph after infernalis, which should be caused by librbd code change. |
rbd_open didn't initialize image_wathcer which will be used later for notification. It will cause go-ceph client crash. Signed-off-by: tdsparrow <sqallowlee@gmail.com>
rbd_open didn't initialize image_wathcer which will be used later for notification. It will cause go-ceph client crash. Signed-off-by: Ren Li <sqallowlee@gmail.com>
I'm trying to get caught up on go-ceph issues, sorry about the delay. Do I understand correctly that the code works ok before infernalis and is broken after infernalis? |
how hard would it be to provide a code snipper that reproduces the problem? |
oh, i'm just using rdb-docker-plugin. didn't actually write the code. |
@noahdesu you are right, this issue won't happen on hammer at least. I also met this issue when using rbd-docker-plugin on recent jewel release. I just made some comments on ceph/ceph#9660 and hope to fix this issue soon. If you would like to reproduce it, here is a golang code snippet, but pls ensure rbd image is existed before you run this code.
|
Perfect, thanks. That will make things much easier! |
Hello, I'm automatically closing all issues filed prior to 2018 that have not been commented on recently. If this issue is still relevant to you please reopen the issue and restart the discussion. Thank you for your understanding. |
I'm using rbd-docker-plugin and it crashed when calling LockExclusive.
here's my env,
CentOS 7.2 with kernel 4.5.3-1.el7.elrepo.x86_64,
ceph version 10.2.1 (3a66dd4f30852819c1bdaa8ec23c795d4ad77269)
librados2 & librbd1 1:10.2.1-0.el7
I couldn't see any relevant log messages, in dmesg, i see this usually (it didn't crash if the image is already lock and return a error message that says it can't get the exclusive lock)
however when it crash, there's no such messages in the dmesg.
btw, the lock is created and locking an image using rdb command directly works fine.
The text was updated successfully, but these errors were encountered: