Bug 2251768 - [GSS] [5.3.z backport] We can not get attributes (getattr) for a specific inode which makes production workload hang.
Summary: [GSS] [5.3.z backport] We can not get attributes (getattr) for a specific ino...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: CephFS
Version: 5.3
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
: 5.3z6
Assignee: Venky Shankar
QA Contact: Hemanth Kumar
Ranjini M N
URL:
Whiteboard:
Depends On: 2251258 2251767 2262740 2266545
Blocks: 2258797
TreeView+ depends on / blocked
 
Reported: 2023-11-27 13:55 UTC by Bipin Kunal
Modified: 2024-02-28 07:34 UTC (History)
12 users (show)

Fixed In Version: ceph-16.2.10-221.el8cp
Doc Type: Bug Fix
Doc Text:
.The loner member is set to `true` Previously, for a file lock in the LOCK_EXCL_XSYN state, the non-loner clients would be issued empty caps. However, since the loner of this state is set to `false`, it could make the locker to issue the Fcb caps to them, which is incorrect. This would cause some client requests to incorrectly revoke some caps and infinitely wait and cause slow requests. With this fix, the loner member is set to `true` and as a result the corresponding request is not blocked.
Clone Of: 2251767
Environment:
Last Closed: 2024-02-08 16:57:00 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-7965 0 None None None 2023-11-27 13:58:36 UTC
Red Hat Product Errata RHSA-2024:0745 0 None None None 2024-02-08 16:57:05 UTC

Comment 13 errata-xmlrpc 2024-02-08 16:57:00 UTC 
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 5.3 Security 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-2024:0745
Note You need to log in before you can comment on or make changes to this bug.