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

Yes, I'm talking about the "writing to fuse device failed:" warning. This is a harmless warning. I have discussed it with Csaba. I'm not aware of the other messages. If heal messages are one of them, have requested Karthik from the AFR team to look into it. The rest of the concerns raised are

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

Hari, Are you talking about "writing to fuse device failed: No such file or directory" or all the messages I've encountered during the 5.13 -> 7.5 upgrade? Because it was more than just logs that went wrong - also healing. Could you please analyze and respond to the relevant thread so we can

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

Hi everyone, So because upgrading introduces additional problems, does this means I should stick with 5.x even if it is EOL? Or what is a "safe" version to upgrade to? Regards, Mabi ‐‐‐ Original Message ‐‐‐ On Wednesday, May 6, 2020 2:44 AM, Artem Russakovskii wrote: > Hi Hari, > >

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

Hi, We understand the concern about facing a bad migration. Most of this is because of the logging issues. These log messages are harmless and are necessary for debugging purposes. We have just backported the fix to the release branches. This fix will reduce this particular log to debug, so it

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

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 , APK Mirror , Illogical Robot LLC beerpla.net |

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

Dear Hari, Thank you for your answer. A few months ago when I reported this issue initially I was told that the fix would be backported to 5.x, at that time 5.x was not EOL. So I guess I should upgrade to 7 but reading this list it seems that version 7 has a few other open issues. Is it safe

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

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

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

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

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

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] (-->

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

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

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

Alright. Built and installed origin/release-6 with the cherry-pick mentioned by Amar and it looks good. No error logs. On Tue, Mar 3, 2020, 11:54 AM Danny Lee wrote: > Tried building off of release-6 with the cherry-pick, but reached a > blocking point due to bugzilla ID 1683574 bug. So I

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

Tried building off of release-6 with the cherry-pick, but reached a blocking point due to bugzilla ID 1683574 bug. So I couldn't test it. On Tue, Mar 3, 2020, 11:04 AM Danny Lee wrote: > I tested a cluster with version 6.7. It's still happening. I was able to > reproduce the log by just

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

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 wrote: > On March 3, 2020 7:27:03

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

On March 3, 2020 7:27:03 AM GMT+02:00, "Felix Kölzow" 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

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

‐‐‐ Original Message ‐‐‐ On Tuesday, March 3, 2020 6:11 AM, Hari Gowtham wrote: > I checked on the backport and found that this patch hasn't yet been > backported to any of the release branches. > If this is the fix, it would be great to have them backported for the next > release.

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

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.

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

Hi Amar, I checked on the backport and found that this patch hasn't yet been backported to any of the release branches. If this is the fix, it would be great to have them backported for the next release. On Tue, Mar 3, 2020 at 7:22 AM Amar Tumballi wrote: > This is not normal at all. > > I

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

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

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

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 wrote: > Hi Felix, > > can you test /on non-prod system/ the latest minor version of

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

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 написа: Dear Community, this message appears for me to on GlusterFS 6.0. Before that, we had GlusterFS

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

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

[Gluster-users] 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] (-->