[Gluster-users] How to solve "check_and_dump_fuse_W"-errors

[Michael Nebel]

Hi,

after several tests, we are very impressed about the stability and
simplicity of gluster. Thanks!

But I need a hint, how to fix the following error:

[2019-10-30 09:18:01.365101] E [fuse-bridge.c:220:check_and_dump_fuse_W]
(-->
/usr/lib64/libglusterfs.so.0(_gf_log_callingfn+0x134)[0x7f8410c4fa34]
(-->
/usr/lib64/glusterfs/6.6/xlator/mount/fuse.so(+0x8e42)[0x7f840fa19e42]
(-->
/usr/lib64/glusterfs/6.6/xlator/mount/fuse.so(+0x9fc0)[0x7f840fa1afc0]
(--> /lib64/libpthread.so.0(+0x8458)[0x7f8410b7a458] (-->
/lib64/libc.so.6(clone+0x3f)[0x7f8410aa5cff] ))))) 0-glusterfs-fuse:
writing to fuse device failed: No such file or directory

The messages occur in the netmount-gluster.log very often (several
tenthousand times a day) and very regularly during larger compiler-jobs.
The binaries and results of the jobs are unaffected. From the user point
of view, everything works fine. But the error-messages are disturbing.

Can you give me any pointer, where to search? Neither BigG or the
sources were of help for me :-(

Thanks

	Michael


-- 
Michael Nebel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3997 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20191030/e222a0af/attachment.p7s>