Upstream ticket: http://tracker.ceph.com/issues/39031
** Bug watch added: tracker.ceph.com/issues #39031
http://tracker.ceph.com/issues/39031
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820976
Tracked via upstream ticket: http://tracker.ceph.com/issues/22120
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731819
Title:
rbd snap_unprotect deadlock
To manage notifications about this bug go
Tracked via upstream ticket: http://tracker.ceph.com/issues/21670
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718134
Title:
rbd refresh_if_required deadlock
To manage notifications about this bu
The v10.2.2 branch with the cherry-picked fix is available under the
'wip-16950-jewel' branch name. See the instructions above for how to
install test/development packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
If you are interested, I can build a Jewel 10.2.2 + this fix
"development" release package [1] that you can install and verify that
it resolves the issue. I am going out of town for a few days so if it's
desired, I would need to know ASAP in order to start the build.
[1] http://docs.ceph.com/docs/
Thanks for the assistance. It appears like the issue you are hitting is
due to a failed watch:
2016-08-12 22:29:45.249895 7f6dc700 -1 librbd::ImageWatcher:
0x7f6db4003b60 image watch failed: 140096867143248, (107) Transport
endpoint is not connected
There is a heartbeat that your client is su
I should also mention that, in the meantime, you may want to disable the
exclusive-lock feature on the affected images via the rbd CLI:
rbd feature disable exclusive-lock,object-map,fast-diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
I think the config option is "log file" instead of "log path". Also,
make sure your QEMU process has access to the directory (both
permissions and AppArmor).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
As an alternative, could you provide the core dump? You can use ceph-
post-file to upload the file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607694
Title:
Exclusive-Lock Issue
To manage notif
Hmm -- any chance either one of you could reproduce with debug logging
enabled? In your ceph configuration file, add the following to the
"[client]" section:
debug rbd = 20
log path = /path/that/is/writable/by/qemu/process/ceph-$pid.log
--
You received this bug notification because you are a mem
@Luis or Daniel: Are you seeing a "image watch failed" error message in
your QEMU librbd logs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607694
Title:
Exclusive-Lock Issue
To manage notificati
Please see the Jewel release notes [1] regarding this change.
Specifically, Ceph, by default, creates new RBD images using features
currently unsupported by krbd. You can disable these features on an
existing image using the 'rbd feature disable' command or you can revert
to pre-Jewel features for
12 matches
Mail list logo