Bug #41229
closedtoo slow to delete a big empty volume
0%
Description
it takes a long time to delete an big empty volume(TB)
Updated by Mykola Golub over 4 years ago
- Status changed from New to In Progress
- Priority changed from Normal to High
- Backport set to nautilus
See the issue discussion in PR 29635 [1]. The regression was introduced when making "rbd_remove" move the image to trash as first step [2]: it has been changed to always run remove request with force flag, and this enforces disabling exclusive lock (to avoid potential exclusive lock acquire failure). As a result the object map is not used during removal.
Jason suggested [3] that it could be fixed by making force first try it w/ the exclusive lock and if acquiring it fails, fall back to the current path where is just ignores it (and therefore object map).
[1] https://github.com/ceph/ceph/pull/29635
[2] https://github.com/ceph/ceph/pull/25438
[3] https://github.com/ceph/ceph/pull/29635#issuecomment-521295618
Updated by Mykola Golub over 4 years ago
- Subject changed from too slow to delete an big empty volume to too slow to delete a big empty volume
Updated by Mykola Golub over 4 years ago
- Pull request ID changed from 29635 to 29775
Changing PR ID from 29635 to 29775, as it contains the real fix.
Updated by Mykola Golub over 4 years ago
- Status changed from In Progress to Fix Under Review
Updated by Jason Dillaman over 4 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Mykola Golub over 4 years ago
- Copied to Backport #41420: nautilus: too slow to delete a big empty volume added
Updated by Nathan Cutler over 4 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".