[Gluster-users] writing to fuse device failed: No such file or directory

Danny Lee dannyl at vt.edu
Tue Mar 3 16:04:32 UTC 2020


I tested a cluster with version 6.7. It's still happening. I was able to
reproduce the log by just copying a large file and then interrupting it
(Ctrl+C).  I guess something in my application is interrupting file io

On Tue, Mar 3, 2020, 3:47 AM Strahil Nikolov <hunter86_bg at yahoo.com> wrote:

> On March 3, 2020 7:27:03 AM GMT+02:00, "Felix Kölzow" <
> felix.koelzow at gmx.de> wrote:
> >Hi Strahil,
> >
> >> can you test /on non-prod system/ the latest minor version of gluster
> >v6 ?
> >on the client side I can update the version to the latest minor
> >version,
> >but the server still
> >
> >remains in v6.0. Actually, we do not have a non-prod gluster system, so
> >it will take some time
> >
> >to do this.
> >
> >Regards,
> >
> >Felix
> >
> >
> >On 02/03/2020 23:25, Strahil Nikolov wrote:
> >> Hi Felix,
> >>
> >> can you test /on non-prod system/ the latest minor version of gluster
> >v6 ?
> >>
> >> Best Regards,
> >> Strahil Nikolov
> >>
> >>
> >> В понеделник, 2 март 2020 г., 21:43:48 ч. Гринуич+2, Felix Kölzow
> ><felix.koelzow at gmx.de> написа:
> >>
> >>
> >>
> >>
> >>
> >> 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
> >> ________
> >>
> >>
> >>
> >> 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
>
> If the isssue is fixed by the commit mentioned by Amar Tumbali, once it is
> in the branches - you will most probably need to upgrade the cluster and
> the clients.
>
> It will be nice to setup a test cluster (with reduced data, but still same
> kind of files) in order to verify that the upgrade will be fine.
>
> Some people are lucky to have a test environment that is actually
> separated from the Prod :)
>
> Best Regards,
> Strahil Nikolov
> ________
>
>
>
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20200303/517c3195/attachment.html>


More information about the Gluster-users mailing list