Blob Blame History Raw
From bd091bbd91555dad98d23d09977db8cb2bdddf39 Mon Sep 17 00:00:00 2001
From: Pranith Kumar K <pkarampu@redhat.com>
Date: Tue, 29 Aug 2017 11:29:33 +0530
Subject: [PATCH 606/613] gluster-block: strict-o-direct should be on

        Backport of https://review.gluster.org/18120

tcmu-runner is not going to open block with O_SYNC anymore
so writes have a chance of getting cached in write-behind
when that happens, there is a chance that on failover some
data could be stuck in cache and be lost.

 >BUG: 1485962
 >Change-Id: If9835d914821dfc4ff432dc96775677a55d2918f
 >Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

BUG: 1486115
Change-Id: If9835d914821dfc4ff432dc96775677a55d2918f
Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
Reviewed-on: https://code.engineering.redhat.com/gerrit/116643
Tested-by: Prasanna Kalever <prasanna.kalever@redhat.com>
Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
---
 extras/group-gluster-block | 1 +
 1 file changed, 1 insertion(+)

diff --git a/extras/group-gluster-block b/extras/group-gluster-block
index 82bd6ff..e94f834 100644
--- a/extras/group-gluster-block
+++ b/extras/group-gluster-block
@@ -4,6 +4,7 @@ performance.io-cache=off
 performance.stat-prefetch=off
 performance.open-behind=off
 performance.readdir-ahead=off
+performance.strict-o-direct=on
 network.remote-dio=disable
 cluster.eager-lock=disable
 cluster.quorum-type=auto
-- 
2.9.5