Actions
Bug #62278
closedpybind/mgr/volumes: pending_subvolume_deletions count is always zero in fs volume info output
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Administration/Usability
Target version:
% Done:
100%
Source:
Tags:
backport_processed
Backport:
pacific,quincy,reef
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
Even after deleting multiple subvolumes, the pending_subvolume_deletions count is always zero
kotresh:build$ bin/ceph fs volume info a *** DEVELOPER MODE: setting PATH, PYTHONPATH and LD_LIBRARY_PATH *** 2023-08-02T15:58:32.709+0530 7fe68149e6c0 -1 WARNING: all dangerous and experimental features are enabled. 2023-08-02T15:58:32.716+0530 7fe68149e6c0 -1 WARNING: all dangerous and experimental features are enabled. { "mon_addrs": [ "10.76.98.126:40039" ], "pending_subvolume_deletions": 0, "pools": { "data": [ { "avail": 106114146304, "name": "cephfs.a.data", "used": 20480 } ], "metadata": [ { "avail": 106114146304, "name": "cephfs.a.meta", "used": 174717710 } ] }, "used_size": 439 }
Updated by Kotresh Hiremath Ravishankar 9 months ago
- Status changed from New to Fix Under Review
- Pull request ID set to 52765
Updated by Venky Shankar 9 months ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot 9 months ago
- Copied to Backport #62404: quincy: pybind/mgr/volumes: pending_subvolume_deletions count is always zero in fs volume info output added
Updated by Backport Bot 9 months ago
- Copied to Backport #62405: reef: pybind/mgr/volumes: pending_subvolume_deletions count is always zero in fs volume info output added
Updated by Backport Bot 9 months ago
- Copied to Backport #62406: pacific: pybind/mgr/volumes: pending_subvolume_deletions count is always zero in fs volume info output added
Updated by Venky Shankar 8 months ago
Backport note: also include commit(s) from https://github.com/ceph/ceph/pull/52940
Updated by Konstantin Shalygin 5 months ago
- Status changed from Pending Backport to Resolved
- Target version set to v19.0.0
- % Done changed from 0 to 100
Actions