[Bugs] [Bug 1456225] gluster-block is not working as expected when shard is enabled
bugzilla at redhat.com
bugzilla at redhat.com
Mon May 29 14:12:24 UTC 2017
https://bugzilla.redhat.com/show_bug.cgi?id=1456225
--- Comment #3 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17404 committed in release-3.11 by
Shyamsundar Ranganathan (srangana at redhat.com)
------
commit 1db7887771c748a63f3c46ce72918c98cb6dc208
Author: Pranith Kumar K <pkarampu at redhat.com>
Date: Wed May 24 22:30:29 2017 +0530
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 <pkarampu at redhat.com>
>Reviewed-on: https://review.gluster.org/17387
>Smoke: Gluster Build System <jenkins at build.gluster.org>
>Reviewed-by: Krutika Dhananjay <kdhananj at redhat.com>
>NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
>CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
BUG: 1456225
Change-Id: I9007e6a39098ab0b5d5386367bd07eb5f89cb09e
Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
Reviewed-on: https://review.gluster.org/17404
Smoke: Gluster Build System <jenkins at build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
Reviewed-by: Shyamsundar Ranganathan <srangana at redhat.com>
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list