Actions
Bug #62407
openpybind/mgr/volumes: Document a possible deadlock after a volume deletion.
Status:
Pending Backport
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
backport_processed
Backport:
reef,quincy
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
mgr/volumes
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
When a cephfs volume is deleted, the mgr threads (cloner, purge threads) could take a corresponding thread lock
and block on a call to fs. If a new cephfs volume is created, a few mgr/volumes operations can block indefinitely
on the same lock. So it is recommended to restart the ceph-mgr on cephfs volume deletion and recreation on the
same cluster if mgr/volumes is being used.
Please see disccusions on [1] and [2] for more details.
[1] https://github.com/ceph/ceph/pull/52765#issuecomment-1669607677
[2] https://tracker.ceph.com/issues/49605#note-5
Updated by Kotresh Hiremath Ravishankar 9 months ago
- Component(FS) mgr/volumes added
Updated by Kotresh Hiremath Ravishankar 9 months ago
- Status changed from New to Fix Under Review
- Pull request ID set to 52945
Updated by Kotresh Hiremath Ravishankar 9 months ago
- Backport set to reef,quincy
Updated by Kotresh Hiremath Ravishankar 9 months ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot 9 months ago
- Copied to Backport #62459: quincy: pybind/mgr/volumes: Document a possible deadlock after a volume deletion. added
Updated by Backport Bot 9 months ago
- Copied to Backport #62460: reef: pybind/mgr/volumes: Document a possible deadlock after a volume deletion. added
Actions