[Gluster-users] Constant fuse client crashes "fixed" by setting performance.write-behind: off. Any hope for a 4.1.8 release?

[Artem Russakovskii]

Brandon, I've had performance.write-behind: off for weeks ever since it was
suggested as a fix, but the crashes kept coming.

Sincerely,
Artem

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


On Tue, Mar 19, 2019 at 9:01 AM <brandon at thinkhuge.net> wrote:

> Hey Artem,
>
>
>
> Wondering have you tried this "performance.write-behind: off" setting?
> I've added this to my multiple separate gluster clusters but, I won't know
> until weekend ftp backups run again if it helps with our situation as a
> workaround.
>
>
>
> We need this fixed highest priority I know that though.
>
>
>
> Can anyone please advise what steps can I take to get similar crash log
> information from CentOS 7 yum repo built gluster?  Would that help if I
> shared that?
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20190319/ca7d5fc3/attachment.html>