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

Amar Tumballi amarts at gmail.com
Tue Mar 3 01:51:50 UTC 2020


This is not normal at all.

I guess the fix was
https://github.com/gluster/glusterfs/commit/1166df1920dd9b2bd5fce53ab49d27117db40238

I didn't check if its backported to other release branches.

Csaba, Rinku, hari can you please confirm on this?

Regards,
Amar


On Tue, Mar 3, 2020 at 4:25 AM Danny Lee <dannyl at vt.edu> wrote:

> This was happening for us on our 3-node replicated server.  For one day,
> the log amassed to 3GBs.  Over a week, it took over 15GBs.
>
> Our gluster version is 6.5.
>
> On Mon, Mar 2, 2020, 5:26 PM Strahil Nikolov <hunter86_bg at yahoo.com>
> 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
>> ________
>>
>>
>>
>> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20200303/5afe3642/attachment.html>


More information about the Gluster-users mailing list