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.
https://code.engineering.redhat.com/gerrit/201206 "fuse: occasional logging for fuse device 'weird' write errors" was posted to address this bug.
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