Bug 1286029
Summary: | Data Tiering:File create terminates with "Input/output error" as split brain is observed | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Ashish Pandey <aspandey> | |
Component: | disperse | Assignee: | Ashish Pandey <aspandey> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | urgent | Docs Contact: | ||
Priority: | urgent | |||
Version: | mainline | CC: | asrivast, bugs, byarlaga, dlambrig, nchilaka, spalai | |
Target Milestone: | --- | Keywords: | ZStream | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.8rc2 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | 1286028 | |||
: | 1291557 (view as bug list) | Environment: | ||
Last Closed: | 2016-06-16 13:47:06 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: | 1275751, 1286028 | |||
Bug Blocks: | 1260923, 1285230, 1290363, 1291557, 1358823 |
Comment 1
Vijay Bellur
2015-11-30 07:09:42 UTC
REVIEW: http://review.gluster.org/12816 (storage/posix: Implement .unlink directory) posted (#2) for review on master by Ashish Pandey (aspandey) REVIEW: http://review.gluster.org/12816 (storage/posix: Implement .unlink directory) posted (#3) for review on master by Ashish Pandey (aspandey) REVIEW: http://review.gluster.org/12816 (storage/posix: Implement .unlink directory) posted (#4) for review on master by Ashish Pandey (aspandey) REVIEW: http://review.gluster.org/12816 (storage/posix: Implement .unlink directory) posted (#5) for review on master by Ashish Pandey (aspandey) REVIEW: http://review.gluster.org/12816 (storage/posix: Implement .unlink directory) posted (#6) for review on master by Vijay Bellur (vbellur) REVIEW: http://review.gluster.org/12816 (storage/posix: Implement .unlink directory) posted (#7) for review on master by Vijay Bellur (vbellur) REVIEW: http://review.gluster.org/12816 (storage/posix: Implement .unlink directory) posted (#8) for review on master by Ashish Pandey (aspandey) REVIEW: http://review.gluster.org/12816 (storage/posix: Implement .unlink directory) posted (#9) for review on master by Ashish Pandey (aspandey) REVIEW: http://review.gluster.org/12816 (storage/posix: Implement .unlink directory) posted (#10) for review on master by Ashish Pandey (aspandey) REVIEW: http://review.gluster.org/12816 (storage/posix: Implement .unlink directory) posted (#11) for review on master by Ashish Pandey (aspandey) COMMIT: http://review.gluster.org/12816 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit c4f6521dfe6a44cee2f61ae41fc26faaf785372d Author: Ashish Pandey <aspandey> Date: Thu Nov 26 14:35:49 2015 +0530 storage/posix: Implement .unlink directory Problem: For EC volume, If a file descriptor is open and file has been unlinked, any further write on that fd will fail. When a write request comes, EC internally reads some blocks using anonymous fd. This read will fail as the file has already been unlinked. Solution: To solve this issue, we are using .unlink directory to keep track of unlinked file. If a file is to be unlinked while its fd is open, move this to .unlink directory and unlink it from .glusterfs and real path. Once all the fd will be closed, remove this entry form .unlink directory. Change-Id: I8344edb0d340bdb883dc46458c16edbc336916b9 BUG: 1286029 Signed-off-by: Ashish Pandey <aspandey> Reviewed-on: http://review.gluster.org/12816 Reviewed-by: Krutika Dhananjay <kdhananj> Reviewed-by: Xavier Hernandez <xhernandez> Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Pranith Kumar Karampuri <pkarampu> This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions 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.8.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |