Bug 2224230
Summary: | client: wait rename to finish | |||
---|---|---|---|---|
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, tserlin, vshankar | |
Target Milestone: | --- | |||
Target Release: | 6.1z2 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | ceph-17.2.6-128.el9cp | Doc Type: | Bug Fix | |
Doc Text: |
.Thread renaming no longer fails
Previously, in a few rare cases, during renaming, if another thread tried to lookup the dst dentry, there were chances for it to get inconsistent result, wherein both the src dentry and dst dentry would link to the same inode simultaneously. Due to this,the rename request would fail as two different dentries were being linked to the same inode.
With this fix, the thread waits for the renaming action to finish and everything works as expected.
|
Story Points: | --- | |
Clone Of: | ||||
: | 2224232 (view as bug list) | Environment: | ||
Last Closed: | 2023-10-12 16:34:33 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 2235257 |
Description
Xiubo Li
2023-07-20 08:24:03 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 (Moderate: Red Hat Ceph Storage 6.1 security, enhancement, and 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/RHSA-2023:5693 |