From bea02e26a3967a6e679e30fbb77ecfeff1e71f37 Mon Sep 17 00:00:00 2001 From: Pranith Kumar K Date: Wed, 24 May 2017 22:30:29 +0530 Subject: features/shard: Handle offset in appending writes When a file is opened with append, all writes are appended at the end of file irrespective of the offset given in the write syscall. This needs to be considered in shard size update function and also for choosing which shard to write to. At the moment shard piggybacks on queuing from write-behind xlator for ordering of the operations. So if write-behind is disabled and two parallel appending-writes come both of which can increase the file size beyond shard-size the file will be corrupted. BUG: 1455301 Change-Id: I9007e6a39098ab0b5d5386367bd07eb5f89cb09e Signed-off-by: Pranith Kumar K Reviewed-on: https://review.gluster.org/17387 Smoke: Gluster Build System Reviewed-by: Krutika Dhananjay NetBSD-regression: NetBSD Build System CentOS-regression: Gluster Build System --- extras/group-gluster-block | 1 - 1 file changed, 1 deletion(-) (limited to 'extras/group-gluster-block') diff --git a/extras/group-gluster-block b/extras/group-gluster-block index 0753d26b3ca..a4a6367920b 100644 --- a/extras/group-gluster-block +++ b/extras/group-gluster-block @@ -2,7 +2,6 @@ performance.quick-read=off performance.read-ahead=off performance.io-cache=off performance.stat-prefetch=off -performance.write-behind=off performance.open-behind=off performance.readdir-ahead=off network.remote-dio=enable -- cgit