<div dir="ltr">Hari,<div><br></div><div>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 figure out what went wrong and fix it?</div><div><br></div><div>Thanks.</div><div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><br>Sincerely,<br>Artem<br><br>--<br>Founder, <a href="http://www.androidpolice.com" target="_blank">Android Police</a>, <a href="http://www.apkmirror.com/" style="font-size:12.8px" target="_blank">APK Mirror</a><span style="font-size:12.8px">, Illogical Robot LLC</span></div><div dir="ltr"><a href="http://beerpla.net/" target="_blank">beerpla.net</a> | <a href="http://twitter.com/ArtemR" target="_blank">@ArtemR</a><br></div></div></div></div></div></div></div></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, May 6, 2020 at 2:16 AM Hari Gowtham <<a href="mailto:hgowtham@redhat.com">hgowtham@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi,</div><div><br></div><div>We understand the concern about facing a bad migration. <br></div><div>Most of this is because of the logging issues. <br></div><div>These log messages are harmless and are necessary for debugging purposes.</div><div> We have just backported the fix to the release branches.</div><div>This fix will reduce this particular log to debug, so it will be clear that it is not harmful.</div><div>We will also look into compressing the log messages even more than we do now.</div><div>Apart from these, to actually make use of this log message for debugging certain issue, <br></div><div>we need certain tunings to be done during the mount.</div><div><a class="gmail_plusreply" id="gmail-m_6068914614716572649m_5111863994442540945plusReplyChip-0" href="mailto:csaba@redhat.com" target="_blank">@Csaba Henk</a> will let you know the tunings necessary.</div><div><br></div><div>5.x to 7.x is supported, 5.x to 8.x will not be supported. And we do recommend testing the setup and</div><div> then using them for production purposes.<br></div><div>Regarding open bugs, Most of the fixes will make its way to the latest releases but might not make it to older releases.</div><div>And just because it was opened on release-7 doesn't mean the bug is not applicable on release-5 (most of the times)<br></div><div>So theoretically newer releases are supposed to be more stable. <br></div><div>Most of the times the older branches look stable because of the corner bug which is hit for one user is not applicable for the other. <br></div><div>As this bug hasn't been hit for a particular user, doesn't mean they are more stable. <br></div><div>All these bugs that we face are backported and fixed in the newer versions, so they are supposed to be even more stable.</div><div>A few bugs might not be backported to older versions due to various reasons.<br></div><div><br></div><div>If you have faced any other major issue with the latest binaries, please do let us know, so we will try to iron them out.</div><div>It would be great if we could get some help with backporting the patches. </div><div>Backporting is relatively easy and if the users help with backporting the issues they come across, <br></div><div>it will help each other with the fixes being made available for everyone and a more stable release. <br></div><div>For a backport, you need to apply the patch from master to the particular release branch</div><div>and send the patch to the respective branch with the same changeid.<br></div><div>One of the reasons this issue (flooding of harmless logs) persisted so long is because we missed to backport.</div><div>So please do help us.<br></div><div><br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, May 6, 2020 at 1:16 PM mabi <<a href="mailto:mabi@protonmail.ch" target="_blank">mabi@protonmail.ch</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>Hi everyone,<br></div><div><br></div><div>So because upgrading introduces additional problems, does this means I should stick with 5.x even if it is EOL?<br></div><div><br></div><div>Or what is a "safe" version to upgrade to?<br></div><div><br></div><div>Regards,<br></div><div>Mabi<br></div><div><div><br></div></div><div><br></div><div>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br></div><div> On Wednesday, May 6, 2020 2:44 AM, Artem Russakovskii <<a href="mailto:archon810@gmail.com" target="_blank">archon810@gmail.com</a>> wrote:<br></div><div> <br></div><blockquote type="cite"><div dir="ltr"><div>Hi Hari,<br></div><div><br></div><div><div>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. <br></div><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><br></div><div>Sincerely,<br></div><div>Artem<br></div><div><br></div><div>--<br></div><div>Founder, <a href="http://www.androidpolice.com" target="_blank">Android Police</a>, <a href="http://www.apkmirror.com/" style="font-size:12.8px" target="_blank">APK Mirror</a><span style="font-size:12.8px">, Illogical Robot LLC</span><br></div></div><div dir="ltr"><a href="http://beerpla.net/" target="_blank">beerpla.net</a> | <a href="http://twitter.com/ArtemR" target="_blank">@ArtemR</a><br></div></div></div></div></div></div></div></div></div></div></div></div></div><div><br></div></div></div><div><br></div><div class="gmail_quote"><div dir="ltr">On Tue, May 5, 2020 at 4:41 AM Hari Gowtham <<a href="mailto:hgowtham@redhat.com" target="_blank">hgowtham@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi,<br></div><div><br></div><div>I don't see the above mentioned fix to be backported to any branch. <br></div><div>I have just cherry picked them for the release-6 and 7.<br></div><div>Release-5 has reached EOL and so, it won't have the fix.<br></div><div>Note: release 6 will have one more release and will be EOLed as well.<br></div><div>Release-8 is being worked on and it will have the fix as a part of the way it's branched. <br></div><div>Once it gets merged, it should be available in the release-6 and 7. but I do recommend switching from <br></div><div>the older branches to the newer ones (at least release-7 in this case).<br></div><div><br></div><div><div><br></div><div><a href="https://review.gluster.org/#/q/change:I510158843e4b1d482bdc496c2e97b1860dc1ba93" target="_blank">https://review.gluster.org/#/q/change:I510158843e4b1d482bdc496c2e97b1860dc1ba93</a><br></div></div></div><div><br></div><div class="gmail_quote"><div dir="ltr">On Tue, May 5, 2020 at 11:52 AM mabi <<a href="mailto:mabi@protonmail.ch" target="_blank">mabi@protonmail.ch</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>Dear Artem,<br></div><div><br></div><div>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.<br></div><div><br></div><div>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.<br></div><div><br></div><div>Best regards,<br></div><div>Mabi<br></div><div><div><div><br></div></div><div><br></div></div><div><br></div><div>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br></div><div>On Monday, May 4, 2020 9:57 PM, Artem Russakovskii <<a href="mailto:archon810@gmail.com" target="_blank">archon810@gmail.com</a>> wrote:<br></div><div><br></div><blockquote type="cite"><div dir="ltr"><div>I'm on 5.13, and these are the only error messages I'm still seeing (after downgrading from the failed v7 update):<br></div><div><br></div><div><div>[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<br></div><div>[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<br></div><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><br></div><div>Sincerely,<br></div><div>Artem<br></div><div><br></div><div>--<br></div><div>Founder, <a href="http://www.androidpolice.com" target="_blank">Android Police</a>, <a href="http://www.apkmirror.com/" style="font-size:12.8px" target="_blank">APK Mirror</a><span style="font-size:12.8px">, Illogical Robot LLC</span><br></div></div><div dir="ltr"><a href="http://beerpla.net/" target="_blank">beerpla.net</a> | <a href="http://twitter.com/ArtemR" target="_blank">@ArtemR</a><br></div></div></div></div></div></div></div></div></div></div></div></div></div><div><br></div></div></div><div><br></div><div class="gmail_quote"><div dir="ltr">On Mon, May 4, 2020 at 5:46 AM mabi <<a href="mailto:mabi@protonmail.ch" target="_blank">mabi@protonmail.ch</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>Hello,<br></div><div><br></div><div>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?<br></div><div><br></div><div>Thanks and regards,<br></div><div>Mabi<br></div><div><br></div><div>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br></div><div>On Monday, March 2, 2020 3:17 PM, mabi <<a href="mailto:mabi@protonmail.ch" target="_blank">mabi@protonmail.ch</a>> wrote:<br></div><div><br></div><div>> Hello,<br></div><div>><br></div><div>> On the FUSE clients of my GlusterFS 5.11 two-node replica+arbitrer I see quite a lot of the following error message repeatedly:<br></div><div>><br></div><div>> [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<br></div><div>><br></div><div>> Both the server and clients are Debian 9.<br></div><div>><br></div><div>> What exactly does this error message mean? And is it normal? or what should I do to fix that?<br></div><div>><br></div><div>> Regards,<br></div><div>> Mabi<br></div><div><br></div><div><br></div><div>________<br></div><div><br></div><div><br></div><div><br></div><div>Community Meeting Calendar:<br></div><div><br></div><div>Schedule -<br></div><div>Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC<br></div><div>Bridge: <a href="https://bluejeans.com/441850968" rel="noreferrer" target="_blank">https://bluejeans.com/441850968</a><br></div><div><br></div><div>Gluster-users mailing list<br></div><div><a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br></div><div><a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br></div></blockquote></div></blockquote><div><br></div><div>________<br></div><div> <br></div><div> <br></div><div> <br></div><div> Community Meeting Calendar:<br></div><div> <br></div><div> Schedule -<br></div><div> Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC<br></div><div> Bridge: <a href="https://bluejeans.com/441850968" rel="noreferrer" target="_blank">https://bluejeans.com/441850968</a><br></div><div> <br></div><div> Gluster-users mailing list<br></div><div> <a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br></div><div> <a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br></div></blockquote></div><div><br></div><div><br></div><div>-- <br></div><div dir="ltr"><div>Regards,<br></div><div>Hari Gowtham.<br></div></div></blockquote></div></blockquote><div><br></div></blockquote></div><br clear="all"><br>-- <br><div dir="ltr">Regards,<br>Hari Gowtham.</div>
</blockquote></div>