<div dir="auto">Due to this issue, along with few other logging issues, we did make a glusterfs-5.5 release, which has the fix for particular crash.<div dir="auto"><br></div><div dir="auto">Regards,</div><div dir="auto">Amar</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 19 Mar, 2019, 1:04 AM , <<a href="mailto:brandon@thinkhuge.net">brandon@thinkhuge.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="#0563C1" vlink="#954F72"><div class="m_-6922874925156956448WordSection1"><p class="MsoNormal">Hello Ville-Pekka and list,<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">I believe we are experiencing similar gluster fuse client crashes on 5.3 as mentioned here. This morning I made a post in regards.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><a href="https://lists.gluster.org/pipermail/gluster-users/2019-March/036036.html" target="_blank" rel="noreferrer">https://lists.gluster.org/pipermail/gluster-users/2019-March/036036.html</a><u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Has this "performance.write-behind: off" setting continued to be all you needed to workaround the issue?<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Thanks,<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Brandon<u></u><u></u></p></div></div>_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank" rel="noreferrer">Gluster-users@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a></blockquote></div>