Bug 1839137

Summary: FUSE protocol status indication suppressed
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Csaba Henk <csaba>
Component: fuseAssignee: Csaba Henk <csaba>
Status: CLOSED ERRATA QA Contact: Pranav Prakash <prprakas>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rhgs-3.5CC: arukumar, puebele, rhs-bugs, rkothiya, sheggodu, storage-qa-internal
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.5.z Batch Update 3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-6.0-38 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-17 04:51:50 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 Csaba Henk 2020-05-22 14:52:07 UTC
Non-posix errnos of writing to /dev/fuse used to be logged at error severity, which was wrong, as these are not an error condition but expected feedback from kernel's fuse component. This was addressed in scope of Bug 1763208 by https://code.engineering.redhat.com/gerrit/189056, and said messages were degraded to debug severity, with the effect of making them invisible in a production setup.

That's however the other extreme: while sporadic occurrence of the fuse status indicated by these errnos doesn't make a difference, when they show up in high numbers is a diagnostically relevant condition (it indicates a suboptimal setting of certain Glusterfs tunables).

So we need batch reporting for these errnos.

Comment 1 Csaba Henk 2020-05-22 15:02:35 UTC
https://code.engineering.redhat.com/gerrit/201206 "fuse: occasional logging for fuse device 'weird' write errors" was posted to address this bug.

Comment 8 errata-xmlrpc 2020-12-17 04:51:50 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 (glusterfs bug fix and enhancement 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-2020:5603