Nope. If I enable write-behind the corruption happens every time.
Il 19/01/2018 08:26, Ing. Luca
Lazzeroni - Trend Servizi Srl ha scritto:
After other test (I'm trying to convice myself about gluster
reliability :-) I've found that with
performance.write-behind off
the vm works without problem. Now I'll try with write-behind on
and flush-behind on too.
Il 18/01/2018 13:30, Krutika
Dhananjay ha scritto:
Thanks for that input. Adding Niels since the issue is
reproducible only with libgfapi.
-Krutika
--
Ing. Luca Lazzeroni
Responsabile Ricerca e Sviluppo
Trend Servizi Srl
Tel: 0376/631761
Web: https://www.trendservizi.it
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users
--
Ing. Luca Lazzeroni
Responsabile Ricerca e Sviluppo
Trend Servizi Srl
Tel: 0376/631761
Web: https://www.trendservizi.it
|
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users