Gluster users - Mar 2020 - writing to fuse device failed: No such file or directory

Hello,

On the FUSE clients of my GlusterFS 5.11 two-node replica+arbitrer I see quite a
lot of the following error message repeatedly:

[2020-03-02 14:12:40.297690] E [fuse-bridge.c:219:check_and_dump_fuse_W] (-->
/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(_gf_log_callingfn+0x13e)[0x7f93d5c13cfe]
(-->
/usr/lib/x86_64-linux-gnu/glusterfs/5.11/xlator/mount/fuse.so(+0x789a)[0x7f93d331989a]
(-->
/usr/lib/x86_64-linux-gnu/glusterfs/5.11/xlator/mount/fuse.so(+0x7c33)[0x7f93d3319c33]
(--> /lib/x86_64-linux-gnu/libpthread.so.0(+0x74a4)[0x7f93d4e8f4a4] (-->
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f93d46ead0f] )))))
0-glusterfs-fuse: writing to fuse device failed: No such file or directory

Both the server and clients are Debian 9.

What exactly does this error message mean? And is it normal? or what should I do
to fix that?

Regards,
Mabi

Dear Community,


this message appears for me to on GlusterFS 6.0.

Before that, we had GlusterFS 3.12 and the client log-file was almost
empty. After

upgrading to 6.0 we are facing this log entries.

Regards,

Felix

On 02/03/2020 15:17, mabi wrote:
> Hello,
>
> On the FUSE clients of my GlusterFS 5.11 two-node replica+arbitrer I see
quite a lot of the following error message repeatedly:
>
> [2020-03-02 14:12:40.297690] E [fuse-bridge.c:219:check_and_dump_fuse_W]
(-->
/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(_gf_log_callingfn+0x13e)[0x7f93d5c13cfe]
(-->
/usr/lib/x86_64-linux-gnu/glusterfs/5.11/xlator/mount/fuse.so(+0x789a)[0x7f93d331989a]
(-->
/usr/lib/x86_64-linux-gnu/glusterfs/5.11/xlator/mount/fuse.so(+0x7c33)[0x7f93d3319c33]
(--> /lib/x86_64-linux-gnu/libpthread.so.0(+0x74a4)[0x7f93d4e8f4a4] (-->
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f93d46ead0f] )))))
0-glusterfs-fuse: writing to fuse device failed: No such file or directory
>
> Both the server and clients are Debian 9.
>
> What exactly does this error message mean? And is it normal? or what should
I do to fix that?
>
> Regards,
> Mabi
>
>
>
>
>
> ________
>
>
>
> Community Meeting Calendar:
>
> Schedule -
> Every Tuesday at 14:30 IST / 09:00 UTC
> Bridge: https://bluejeans.com/441850968
>
> Gluster-users mailing list
> Gluster-users at gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users

Hello,

Now that GlusterFS 5.13 has been released, could someone let me know if this
issue (see mail below) has been fixed in 5.13?

Thanks and regards,
Mabi

??????? Original Message ???????
On Monday, March 2, 2020 3:17 PM, mabi <mabi at protonmail.ch> wrote:
> Hello,
>
> On the FUSE clients of my GlusterFS 5.11 two-node replica+arbitrer I see
quite a lot of the following error message repeatedly:
>
> [2020-03-02 14:12:40.297690] E [fuse-bridge.c:219:check_and_dump_fuse_W]
(-->
/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(_gf_log_callingfn+0x13e)[0x7f93d5c13cfe]
(-->
/usr/lib/x86_64-linux-gnu/glusterfs/5.11/xlator/mount/fuse.so(+0x789a)[0x7f93d331989a]
(-->
/usr/lib/x86_64-linux-gnu/glusterfs/5.11/xlator/mount/fuse.so(+0x7c33)[0x7f93d3319c33]
(--> /lib/x86_64-linux-gnu/libpthread.so.0(+0x74a4)[0x7f93d4e8f4a4] (-->
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f93d46ead0f] )))))
0-glusterfs-fuse: writing to fuse device failed: No such file or directory
>
> Both the server and clients are Debian 9.
>
> What exactly does this error message mean? And is it normal? or what should
I do to fix that?
>
> Regards,
> Mabi