Bug 1455301
Summary: | gluster-block is not working as expected when shard is enabled | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Pranith Kumar K <pkarampu> | |
Component: | sharding | Assignee: | Pranith Kumar K <pkarampu> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | bugs <bugs> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | mainline | CC: | bugs, kdhananj, knarra, rhs-bugs, storage-qa-internal | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.12.0 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | 1454313 | |||
: | 1456225 (view as bug list) | Environment: | ||
Last Closed: | 2017-09-05 17:32:07 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1454313 | |||
Bug Blocks: | 1456225 |
Comment 1
Pranith Kumar K
2017-05-24 17:25:56 UTC
REVIEW: https://review.gluster.org/17387 (features/shard: Handle offset in appending writes) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu) REVIEW: https://review.gluster.org/17387 (features/shard: Handle offset in appending writes) posted (#2) for review on master by Pranith Kumar Karampuri (pkarampu) REVIEW: https://review.gluster.org/17387 (features/shard: Handle offset in appending writes) posted (#3) for review on master by Pranith Kumar Karampuri (pkarampu) REVIEW: https://review.gluster.org/17387 (features/shard: Handle offset in appending writes) posted (#4) for review on master by Pranith Kumar Karampuri (pkarampu) COMMIT: https://review.gluster.org/17387 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit bea02e26a3967a6e679e30fbb77ecfeff1e71f37 Author: Pranith Kumar K <pkarampu> 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> Reviewed-on: https://review.gluster.org/17387 Smoke: Gluster Build System <jenkins.org> Reviewed-by: Krutika Dhananjay <kdhananj> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.12.0, please open a new bug report. glusterfs-3.12.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/announce/2017-September/000082.html [2] https://www.gluster.org/pipermail/gluster-users/ |