Bug #46552
Rescue procedure for extremely large bluefs log
% Done:
0%
Source:
Tags:
Backport:
nautilus,octopus,mimic,luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Description
This feature was developed on luminous before being merged into master.
Luminous: https://github.com/ceph/ceph/pull/35776 - tested and verified
Related issues
History
#1 Updated by Neha Ojha over 3 years ago
- Pull request ID changed from 36110 to 36121
#2 Updated by Neha Ojha over 3 years ago
Neha Ojha wrote:
https://github.com/ceph/ceph/pull/36123
Luminous: https://github.com/ceph/ceph/pull/35776 - tested and verified
#3 Updated by Nathan Cutler over 3 years ago
- Backport changed from nautilus,octopus to nautilus,octopus,mimic,luminous
#4 Updated by Nathan Cutler over 3 years ago
- Copied to Backport #46598: luminous: Rescue procedure for extremely large bluefs log added
#5 Updated by Nathan Cutler over 3 years ago
- Copied to Backport #46599: octopus: Rescue procedure for extremely large bluefs log added
#6 Updated by Nathan Cutler over 3 years ago
- Description updated (diff)
#7 Updated by Neha Ojha over 3 years ago
- Status changed from Fix Under Review to Pending Backport
#8 Updated by Nathan Cutler over 3 years ago
- Copied to Backport #46713: mimic: Rescue procedure for extremely large bluefs log added
#9 Updated by Nathan Cutler over 3 years ago
- Copied to Backport #46714: nautilus: Rescue procedure for extremely large bluefs log added
#10 Updated by Nathan Cutler about 3 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".