Actions
Bug #53848
closedmgr/volumes: Failed to create clones if the source snapshot's quota is exceeded
% Done:
0%
Source:
Tags:
backport_processed
Backport:
pacific,octopus,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
The subvolume snapshot clone fails if the quota on the source
has exceeded. Since the quota is not strictly enforced
at the byte range, this is a possibility.
Steps to reproduce:
1. Create a subvolume with 20 MB size
2. Fill the subvolume with 50 files of 1MB each. (This mostly succeeds if written in loop, exceeding the quota)
3. Create subvolume snapshot
4. Clone the snapshot, the clone fails.
Updated by Kotresh Hiremath Ravishankar over 2 years ago
- Status changed from New to In Progress
- Assignee set to Kotresh Hiremath Ravishankar
Updated by Kotresh Hiremath Ravishankar over 2 years ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 44557
Updated by Kotresh Hiremath Ravishankar over 2 years ago
- Backport set to pacific, octopus
Updated by Venky Shankar over 2 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot over 2 years ago
- Copied to Backport #53947: octopus: mgr/volumes: Failed to create clones if the source snapshot's quota is exceeded added
Updated by Backport Bot over 2 years ago
- Copied to Backport #53948: pacific: mgr/volumes: Failed to create clones if the source snapshot's quota is exceeded added
Updated by Kotresh Hiremath Ravishankar about 2 years ago
- Backport changed from pacific, octopus to pacific,octopus,quincy
Updated by Kotresh Hiremath Ravishankar about 2 years ago
- Copied to Backport #54123: quincy:mgr/volumes: Failed to create clones if the source snapshot's quota is exceeded added
Updated by Greg Farnum over 1 year ago
- Status changed from Pending Backport to Resolved
Actions