Bug 1476870
Summary: | [EC]: md5sum mismatches every time for a file from the fuse client on EC volume | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Ashish Pandey <aspandey> |
Component: | disperse | Assignee: | Ashish Pandey <aspandey> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 3.11 | CC: | amukherj, bugs, nchilaka, pkarampu, rcyriac, rhinduja, rhs-bugs, sheggodu, storage-qa-internal |
Target Milestone: | --- | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.11.3 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1476205 | Environment: | |
Last Closed: | 2017-08-24 14:46:21 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: | 1476205 | ||
Bug Blocks: |
Description
Ashish Pandey
2017-07-31 16:31:54 UTC
REVIEW: https://review.gluster.org/17933 (ec/cluster: Update failure of fop on a brick properly) posted (#1) for review on release-3.11 by Ashish Pandey (aspandey) COMMIT: https://review.gluster.org/17933 committed in release-3.11 by Shyamsundar Ranganathan (srangana) ------ commit 49ac61ae11508a16a56534a656d77be47f3fe6b8 Author: Ashish Pandey <aspandey> Date: Fri Jul 28 15:18:29 2017 +0530 ec/cluster: Update failure of fop on a brick properly Problem: In case of truncate, if writev or open fails on a brick, in some cases it does not mark the failure onlock->good_mask. This causes the update of size and version on all the bricks even if it has failed on one of the brick. That ultimately causes a data corruption. Solution: In callback of such writev and open calls, mark fop->good for parent too. Thanks Pranith Kumar K <pkarampu> for finding the root cause. >Change-Id: I8a1da2888bff53b91a0d362b8c44fcdf658e7466 >BUG: 1476205 >Signed-off-by: Ashish Pandey <aspandey> >Reviewed-on: https://review.gluster.org/17906 >Reviewed-by: Pranith Kumar Karampuri <pkarampu> >Smoke: Gluster Build System <jenkins.org> >CentOS-regression: Gluster Build System <jenkins.org> >Signed-off-by: Ashish Pandey <aspandey> Change-Id: I8a1da2888bff53b91a0d362b8c44fcdf658e7466 BUG: 1476870 Signed-off-by: Ashish Pandey <aspandey> Reviewed-on: https://review.gluster.org/17933 Smoke: Gluster Build System <jenkins.org> Reviewed-by: Pranith Kumar Karampuri <pkarampu> 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.11.3, please open a new bug report. glusterfs-3.11.3 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-August/000081.html [2] https://www.gluster.org/pipermail/gluster-users/ |