Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 2244866

Summary: [RHCS 6.1.x clone]: MDS: "1 MDSs behind on trimming" and "2 clients failing to respond to cache pressure".
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Manny <mcaldeir>
Component: CephFSAssignee: Patrick Donnelly <pdonnell>
Status: CLOSED ERRATA QA Contact: Hemanth Kumar <hyelloji>
Severity: high Docs Contact: Disha Walvekar <dwalveka>
Priority: unspecified    
Version: 5.3CC: ceph-eng-bugs, cephqe-warriors, dwalveka, hyelloji, linuxkidd, mcaldeir, pdonnell, tserlin, vereddy, vshankar
Target Milestone: ---   
Target Release: 6.1z4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-17.2.6-179.el9cp Doc Type: Bug Fix
Doc Text:
Cause: MDS may not queue the next client request for replay in the up:client-replay state. Consequence: The MDS would hang in the up:client-replay state. Fix: The next client replay request is queued automatically as part of request clenaup. Result: MDS proceeds with failover recovery normally.
Story Points: ---
Clone Of: 2243105 Environment:
Last Closed: 2024-02-08 18:13:17 UTC Type: ---
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: 2243105, 2244868    
Bug Blocks: 2261930    

Comment 2 Manny 2023-10-19 10:40:32 UTC
The issue, the root cause and the solution will be detailed in KCS #7038973, (https://access.redhat.com/solutions/7038973)
(Do not mark this comment Private)
.

Comment 17 errata-xmlrpc 2024-02-08 18:13:17 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 (Red Hat Ceph Storage 6.1 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-2024:0747