REVIEW: http://review.gluster.org/12968 (storage/posix: Implement .unlink directory) posted (#1) for review on release-3.7 by Ashish Pandey (aspandey)
REVIEW: http://review.gluster.org/12968 (storage/posix: Implement .unlink directory) posted (#2) for review on release-3.7 by Ashish Pandey (aspandey)
REVIEW: http://review.gluster.org/12968 (storage/posix: Implement .unlink directory) posted (#3) for review on release-3.7 by Ashish Pandey (aspandey)
REVIEW: http://review.gluster.org/12968 (storage/posix: Implement .unlink directory) posted (#4) for review on release-3.7 by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/12968 (storage/posix: Implement .unlink directory) posted (#5) for review on release-3.7 by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/12968 (storage/posix: Implement .unlink directory) posted (#6) for review on release-3.7 by Pranith Kumar Karampuri (pkarampu)
COMMIT: http://review.gluster.org/12968 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu) ------ commit 195548f55b09bf71db92929b7b734407b863093c 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. master - http://review.gluster.org/#/c/12816/ Change-Id: I8344edb0d340bdb883dc46458c16edbc336916b9 BUG: 1291557 Signed-off-by: Ashish Pandey <aspandey> Reviewed-on: http://review.gluster.org/12968 Reviewed-by: Pranith Kumar Karampuri <pkarampu> Tested-by: Pranith Kumar Karampuri <pkarampu> Smoke: Gluster Build System <jenkins.com> CentOS-regression: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org>
REVIEW: http://review.gluster.org/13449 (posix: fix posix_fgetxattr to return the correct error) posted (#1) for review on release-3.7 by Susant Palai (spalai)
REVIEW: http://review.gluster.org/13449 (posix: fix posix_fgetxattr to return the correct error) posted (#2) for review on release-3.7 by Susant Palai (spalai)
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.7.7, please open a new bug report. glusterfs-3.7.7 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] https://www.gluster.org/pipermail/gluster-users/2016-February/025292.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user
REVIEW: http://review.gluster.org/13449 (posix: fix posix_fgetxattr to return the correct error) posted (#3) for review on release-3.7 by Susant Palai (spalai)