Bug #40474
closed
client: more precise CEPH_CLIENT_CAPS_PENDING_CAPSNAP
Added by Zheng Yan almost 5 years ago.
Updated about 4 years ago.
Component(FS):
Client, MDS
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.
- Backport set to nautilus,mimic
- Status changed from New to Fix Under Review
- Pull request ID set to 28685
- 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
- Status changed from Fix Under Review to Resolved
- Status changed from Resolved to Pending Backport
- Copied to Backport #41113: nautilus: client: more precise CEPH_CLIENT_CAPS_PENDING_CAPSNAP added
- Copied to Backport #41114: mimic: client: more precise CEPH_CLIENT_CAPS_PENDING_CAPSNAP added
- 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".
Also available in: Atom
PDF