Bug 2224242
Summary: | mds: cap revoke and cap update's seqs mismatched | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Xiubo Li <xiubli> | |
Component: | CephFS | Assignee: | Xiubo Li <xiubli> | |
Status: | CLOSED ERRATA | QA Contact: | Hemanth Kumar <hyelloji> | |
Severity: | medium | Docs Contact: | Akash Raj <akraj> | |
Priority: | unspecified | |||
Version: | 5.3 | CC: | akraj, ceph-eng-bugs, cephqe-warriors, rmandyam, tserlin, vshankar | |
Target Milestone: | --- | |||
Target Release: | 5.3z5 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | ceph-16.2.10-203.el8cp | Doc Type: | Bug Fix | |
Doc Text: |
.Metadata updates are no longer missed or lost
Previously, before the revoke request, which increases the `seq`, was sent out, the clients released the corresponding caps and sent out the cap update request with old `seq`. The MDS would miss checking the `seq` and calculating the caps. Due to this, certain metadatas’ updation would be missed.
With this fix, an acknowledgement is always sent for revoke requests and the metadata is always successfully and correctly updated.
|
Story Points: | --- | |
Clone Of: | ||||
: | 2224243 (view as bug list) | Environment: | ||
Last Closed: | 2023-08-28 09:40:56 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: |
Description
Xiubo Li
2023-07-20 09:04:19 UTC
Please specify the severity of this bug. Severity is defined here: https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat Ceph Storage 5.3 Bug Fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:4760 |