Bug 1585029
Summary: | [CephFS]: Client IO's hung Fuse service asserted with error FAILED assert(oset.objects.empty() | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Yan, Zheng <zyan> |
Component: | CephFS | Assignee: | Patrick Donnelly <pdonnell> |
Status: | CLOSED ERRATA | QA Contact: | Ramakrishnan Periyasamy <rperiyas> |
Severity: | medium | Docs Contact: | John Brier <jbrier> |
Priority: | high | ||
Version: | 3.1 | CC: | agunn, ceph-eng-bugs, ceph-qe-bugs, hnallurv, jbrier, john.spray, pdonnell, rperiyas, tserlin, vakulkar, zyan |
Target Milestone: | rc | ||
Target Release: | 3.1 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | RHEL: ceph-12.2.5-20.el7cp Ubuntu: ceph-12.2.5-10redhat1xenial | Doc Type: | Bug Fix |
Doc Text: |
.Client I/O sometimes fails for CephFS FUSE clients
Client I/O sometimes failed for Ceph File System (CephFS) as a File System in User Space (FUSE) client with the error `transport endpoint shutdown` due to an assert in the FUSE service. With this update to {product}, the issue is resolved.
|
Story Points: | --- |
Clone Of: | 1576908 | Environment: | |
Last Closed: | 2018-09-26 18:21:13 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: | 1576908 | ||
Bug Blocks: | 1576030, 1584264 |
Comment 3
Yan, Zheng
2018-06-01 08:28:57 UTC
Moving this bug to verified state. Not observed any MDS crash during MDS in starting/stopping or resolve state. Automation regression suite run: http://cistatus.ceph.redhat.com/ui/#cephci/launches/all%7Cpage.page=2&page.size=50&page.sort=start_time,number%2CDESC/5b3f836536d1a00001ee66e0?page.page=1&page.size=50&page.sort=start_time%2CASC 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, 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-2018:2819 |