Bug #21558
closedrbd ls -l crashes with SIGABRT
0%
Description
We've been upgrading our cluster from Hammer to Jewel, the upgrade has completed, sortbitwise and require_jewel_osds are set, clients (libvirt/qemu) are connected and fully working.
Now, rbd ls -l crashes for 1 of our 2 pools. RBD crash log with debugging symbols attached.
Files
Updated by Jérôme Poulin over 6 years ago
After trying rbd from Hammer and Infernalis, both are able to use rbd ls -l on the problematic pool on the remote cluster, however, rbd from Jewel and Luminous aren't working.
Updated by Jérôme Poulin over 6 years ago
I'd like to update my issue to change the release to Jewel.
Our cluster is at version 10.2.9 (2ee413f77150c0f375ff6f10edd6c8f9c7d060d0) and the tools I'm using are rbd from either version 10.2.9 or version 12.2.0.
Updated by Brad Hubbard over 6 years ago
- Project changed from Ceph to rbd
- Category deleted (
librbd)
Updated by Jason Dillaman over 6 years ago
- Status changed from New to In Progress
- Assignee set to Jason Dillaman
- Backport set to luminous,jewel
Updated by Jason Dillaman over 6 years ago
- Status changed from In Progress to Fix Under Review
Updated by Jérôme Poulin over 6 years ago
After testing RBD from this branch/PR on our Jewel cluster, the problem has been resolved and ls -l is working properly.
Updated by Mykola Golub over 6 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler over 6 years ago
- Copied to Backport #21641: luminous: rbd ls -l crashes with SIGABRT added
Updated by Nathan Cutler over 6 years ago
- Copied to Backport #21642: jewel: rbd ls -l crashes with SIGABRT added
Updated by Nathan Cutler about 6 years ago
- Status changed from Pending Backport to Resolved