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

2020-05-04 Thread Artem Russakovskii 
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 , APK Mirror
, Illogical Robot LLC
beerpla.net | @ArtemR 


On Mon, May 4, 2020 at 5:46 AM mabi  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  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@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@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

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

2020-05-04 Thread mabi 
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  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@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Upgrade from 5.13 to 7.5 full of weird messages

2020-05-04 Thread Amar Tumballi 
On Sat, May 2, 2020 at 10:49 PM Artem Russakovskii 
wrote:

> I don't have geo replication.
>
> Still waiting for someone from the gluster team to chime in. They used to
> be a lot more responsive here. Do you know if there is a holiday perhaps,
> or have the working hours been cut due to Coronavirus currently?
>
>
It was Holiday on May 1st, and 2nd and 3rd were Weekend days!  And also I
guess many of Developers from Red Hat were attending Virtual Summit!



> I'm not inclined to try a v6 upgrade without their word first.
>

Fair bet! I will bring this topic in one of the community meetings, and ask
developers if they have some feedback! I personally have not seen these
errors, and don't have a hunch on which patch would have caused an increase
in logs!

-Amar


>
> On Sat, May 2, 2020, 12:47 AM Strahil Nikolov 
> wrote:
>
>> On May 1, 2020 8:03:50 PM GMT+03:00, Artem Russakovskii <
>> archon...@gmail.com> wrote:
>> >The good news is the downgrade seems to have worked and was painless.
>> >
>> >zypper install --oldpackage glusterfs-5.13, restart gluster, and almost
>> >immediately there are no heal pending entries anymore.
>> >
>> >The only things still showing up in the logs, besides some healing is
>> >0-glusterfs-fuse:
>> >writing to fuse device failed: No such file or directory:
>> >==> mnt-androidpolice_data3.log <==
>> >[2020-05-01 16:54:21.085643] E
>> >[fuse-bridge.c:219:check_and_dump_fuse_W]
>> >(-->
>> >/usr/lib64/libglusterfs.so.0(_gf_log_callingfn+0x17d)[0x7fd13d50624d]
>> >(-->
>> >/usr/lib64/glusterfs/5.13/xlator/mount/fuse.so(+0x849a)[0x7fd1398e949a]
>> >(-->
>> >/usr/lib64/glusterfs/5.13/xlator/mount/fuse.so(+0x87bb)[0x7fd1398e97bb]
>> >(--> /lib64/libpthread.so.0(+0x84f9)[0x7fd13ca564f9] (-->
>> >/lib64/libc.so.6(clone+0x3f)[0x7fd13c78ef2f] ) 0-glusterfs-fuse:
>> >writing to fuse device failed: No such file or directory
>> >==> mnt-apkmirror_data1.log <==
>> >[2020-05-01 16:54:21.268842] E
>> >[fuse-bridge.c:219:check_and_dump_fuse_W]
>> >(-->
>> >/usr/lib64/libglusterfs.so.0(_gf_log_callingfn+0x17d)[0x7fdf2b0a624d]
>> >(-->
>> >/usr/lib64/glusterfs/5.13/xlator/mount/fuse.so(+0x849a)[0x7fdf2748949a]
>> >(-->
>> >/usr/lib64/glusterfs/5.13/xlator/mount/fuse.so(+0x87bb)[0x7fdf274897bb]
>> >(--> /lib64/libpthread.so.0(+0x84f9)[0x7fdf2a5f64f9] (-->
>> >/lib64/libc.so.6(clone+0x3f)[0x7fdf2a32ef2f] ) 0-glusterfs-fuse:
>> >writing to fuse device failed: No such file or directory
>> >
>> >It'd be very helpful if it had more info about what failed to write and
>> >why.
>> >
>> >I'd still really love to see the analysis of this failed upgrade from
>> >core
>> >gluster maintainers to see what needs fixing and how we can upgrade in
>> >the
>> >future.
>> >
>> >Thanks.
>> >
>> >Sincerely,
>> >Artem
>> >
>> >--
>> >Founder, Android Police , APK Mirror
>> >, Illogical Robot LLC
>> >beerpla.net | @ArtemR 
>> >
>> >
>> >On Fri, May 1, 2020 at 7:25 AM Artem Russakovskii 
>> >wrote:
>> >
>> >> I do not have snapshots, no. I have a general file based backup, but
>> >also
>> >> the other 3 nodes are up.
>> >>
>> >> OpenSUSE 15.1.
>> >>
>> >> If I try to downgrade and it doesn't work, what's the brick
>> >replacement
>> >> scenario - is this still accurate?
>> >>
>> >
>> https://docs.gluster.org/en/latest/Administrator%20Guide/Managing%20Volumes/#replace-brick
>> >>
>> >> Any feedback about the issues themselves yet please? Specifically, is
>> >> there a chance this is happening because of the mismatched gluster
>> >> versions? Though, what's the solution then?
>> >>
>> >> On Fri, May 1, 2020, 1:07 AM Strahil Nikolov 
>> >> wrote:
>> >>
>> >>> On May 1, 2020 1:25:17 AM GMT+03:00, Artem Russakovskii <
>> >>> archon...@gmail.com> wrote:
>> >>> >If more time is needed to analyze this, is this an option? Shut
>> >down
>> >>> >7.5,
>> >>> >downgrade it back to 5.13 and restart, or would this screw
>> >something up
>> >>> >badly? I didn't up the op-version yet.
>> >>> >
>> >>> >Thanks.
>> >>> >
>> >>> >Sincerely,
>> >>> >Artem
>> >>> >
>> >>> >--
>> >>> >Founder, Android Police , APK Mirror
>> >>> >, Illogical Robot LLC
>> >>> >beerpla.net | @ArtemR 
>> >>> >
>> >>> >
>> >>> >On Thu, Apr 30, 2020 at 3:13 PM Artem Russakovskii
>> >>> >
>> >>> >wrote:
>> >>> >
>> >>> >> The number of heal pending on citadel, the one that was upgraded
>> >to
>> >>> >7.5,
>> >>> >> has now gone to 10s of thousands and continues to go up.
>> >>> >>
>> >>> >> Sincerely,
>> >>> >> Artem
>> >>> >>
>> >>> >> --
>> >>> >> Founder, Android Police , APK
>> >Mirror
>> >>> >> , Illogical Robot LLC
>> >>> >> beerpla.net | @ArtemR 
>> >>> >>
>> >>> >>
>> >>> >> On Thu, Apr 30, 2020 at 2:57 PM Artem Russakovskii
>> >>> >
>> >>> >> wrote:
>> >>> >>
>> >>> >>> Hi all,
>> >>> >>>
>> >>> >>> Today,