Why are the messages 'writing to fuse device failed: No such file or directory' spamming Gluster client logs?

Solution Verified - Updated -

Issue

  • The logs of a native Gluster client, stored at /var/log/glusterfs/mount-point.logare filled up with these entries:

    [2021-06-06 07:25:44.992383] E [fuse-bridge.c:220:check_and_dump_fuse_W] (--> /lib64/libglusterfs.so.0(_gf_log_callingfn+0x13b)[0x7fe4c3eb7b0b] (--> /usr/lib64/glusterfs/6.0/xlator/mount/fuse.so(+0x8201)[0x7fe4bb262201] (--> /usr/lib64/glusterfs/6.0/xlator/mount/fuse.so(+0x9938)[0x7fe4bb263938] (--> /lib64/libpthread.so.0(+0x7ea5)[0x7fe4c2cf4ea5] (--> /lib64/libc.so.6(clone+0x6d)[0x7fe4c25ba8cd] ))))) 0-glusterfs-fuse: writing to fuse device failed: No such file or directory

  • Why are these messages showing? How to avoid them?

Environment

  • Red Hat Gluster Storage version 3.5.0 and below.
  • Red Hat Openshift Container Storage version 3.11.4 and below.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content