Actions
Bug #40474
closedclient: more precise CEPH_CLIENT_CAPS_PENDING_CAPSNAP
% Done:
0%
Source:
Development
Tags:
Backport:
nautilus,mimic
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Client, MDS
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
client may set CEPH_CLIENT_CAPS_PENDING_CAPSNAP flag even there is no further cap snap flush. This may confuse mds and cause request on snap inode hang.
Updated by Zheng Yan almost 5 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 28685
Updated by Patrick Donnelly almost 5 years ago
- Assignee set to Zheng Yan
- Target version set to v15.0.0
- Start date deleted (
06/21/2019) - Source set to Development
- Component(FS) Client, MDS added
Updated by Patrick Donnelly over 4 years ago
- Status changed from Fix Under Review to Resolved
Updated by Patrick Donnelly over 4 years ago
- Status changed from Resolved to Pending Backport
Updated by Patrick Donnelly over 4 years ago
- Copied to Backport #41113: nautilus: client: more precise CEPH_CLIENT_CAPS_PENDING_CAPSNAP added
Updated by Patrick Donnelly over 4 years ago
- Copied to Backport #41114: mimic: client: more precise CEPH_CLIENT_CAPS_PENDING_CAPSNAP added
Updated by Nathan Cutler about 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".
Actions