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

[Artem Russakovskii]

Hi Hari,

Hmm, given how poorly our migration from 5.13 to 7.5 went, I am not sure
how I'd move forward with what you suggested at this point.

Sincerely,
Artem

--
Founder, Android Police <http://www.androidpolice.com>, APK Mirror
<http://www.apkmirror.com/>, Illogical Robot LLC
beerpla.net | @ArtemR <http://twitter.com/ArtemR>


On Tue, May 5, 2020 at 4:41 AM Hari Gowtham <hgowtham at redhat.com> wrote:

> Hi,
>
> I don't see the above mentioned fix to be backported to any branch.
> I have just cherry picked them for the release-6 and 7.
> Release-5 has reached EOL and so, it won't have the fix.
> Note: release 6 will have one more release and will be EOLed as well.
> Release-8 is being worked on and it will have the fix as a part of the way
> it's branched.
> Once it gets merged, it should be available in the release-6 and 7. but I
> do recommend switching from
> the older branches to the newer ones (at least release-7 in this case).
>
>
>
> https://review.gluster.org/#/q/change:I510158843e4b1d482bdc496c2e97b1860dc1ba93
>
> On Tue, May 5, 2020 at 11:52 AM mabi <mabi at protonmail.ch> wrote:
>
>> Dear Artem,
>>
>> Thank you for your answer. If you still see these errors messages with
>> GlusterFS 5.13 I suppose then that this bug fix has not been backported to
>> 5.x.
>>
>> Could someone of the dev team please confirm? It was said on this list
>> that this bug fix would be back ported to 5.x, so I am a bit surprised.
>>
>> Best regards,
>> Mabi
>>
>>
>>
>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>> On Monday, May 4, 2020 9:57 PM, Artem Russakovskii <archon810 at gmail.com>
>> wrote:
>>
>> I'm on 5.13, and these are the only error messages I'm still seeing
>> (after downgrading from the failed v7 update):
>>
>> [2020-05-04 19:56:29.391121] E [fuse-bridge.c:219:check_and_dump_fuse_W]
>> (--> /usr/lib64/libglusterfs.so.0(_gf_log_callingfn+0x17d)[0x7f0f9a5f324d]
>> (-->
>> /usr/lib64/glusterfs/5.13/xlator/mount/fuse.so(+0x849a)[0x7f0f969d649a]
>> (-->
>> /usr/lib64/glusterfs/5.13/xlator/mount/fuse.so(+0x87bb)[0x7f0f969d67bb]
>> (--> /lib64/libpthread.so.0(+0x84f9)[0x7f0f99b434f9] (-->
>> /lib64/libc.so.6(clone+0x3f)[0x7f0f9987bf2f] ))))) 0-glusterfs-fuse:
>> writing to fuse device failed: No such file or directory
>> [2020-05-04 19:56:29.400541] E [fuse-bridge.c:219:check_and_dump_fuse_W]
>> (--> /usr/lib64/libglusterfs.so.0(_gf_log_callingfn+0x17d)[0x7f0f9a5f324d]
>> (-->
>> /usr/lib64/glusterfs/5.13/xlator/mount/fuse.so(+0x849a)[0x7f0f969d649a]
>> (-->
>> /usr/lib64/glusterfs/5.13/xlator/mount/fuse.so(+0x87bb)[0x7f0f969d67bb]
>> (--> /lib64/libpthread.so.0(+0x84f9)[0x7f0f99b434f9] (-->
>> /lib64/libc.so.6(clone+0x3f)[0x7f0f9987bf2f] ))))) 0-glusterfs-fuse:
>> writing to fuse device failed: No such file or directory
>>
>> Sincerely,
>> Artem
>>
>> --
>> Founder, Android Police <http://www.androidpolice.com>, APK Mirror
>> <http://www.apkmirror.com/>, Illogical Robot LLC
>> beerpla.net | @ArtemR <http://twitter.com/ArtemR>
>>
>>
>> On Mon, May 4, 2020 at 5:46 AM mabi <mabi at protonmail.ch> wrote:
>>
>>> 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
>>>
>>>
>>> ________
>>>
>>>
>>>
>>> Community Meeting Calendar:
>>>
>>> Schedule -
>>> Every 2nd and 4th 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 2nd and 4th 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
>>
>
>
> --
> Regards,
> Hari Gowtham.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20200505/289ffc6f/attachment.html>