+++ This bug was initially created as a clone of Bug #1242254 +++ Description of problem: Rebalance was failing because ec was giving EIO when lock acquiring fails as the file/dir doesn't exist. Posix_create/mknod are not setting config xattr because internal-fop key is present in dict and setxattr for this fails leading to failure in setting rest of xattrs. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- Additional comment from Anand Avati on 2015-07-12 10:56:33 EDT --- REVIEW: http://review.gluster.org/11639 (cluster/ec: Propogate correct errno in case of failures) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/11688 (cluster/ec: Propogate correct errno in case of failures) posted (#1) for review on release-3.7 by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/11688 (cluster/ec: Propogate correct errno in case of failures) posted (#2) for review on release-3.7 by Xavier Hernandez (xhernandez)
COMMIT: http://review.gluster.org/11688 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu) ------ commit 64344ba16ad996d5bf517c2ca983cc730e1c7117 Author: Pranith Kumar K <pkarampu> Date: Sun Jul 12 18:37:43 2015 +0530 cluster/ec: Propogate correct errno in case of failures - Also remove internal-fop setting in create/mknod etc xattrs. Rebalance was failing because ec was giving EIO when lock acquiring fails as the file/dir doesn't exist. Posix_create/mknod are not setting config xattr because internal-fop key is present in dict and setxattr for this fails leading to failure in setting rest of xattrs. >Change-Id: Ifb429c8db9df7cd51e4f8ce53fdf1e1b975c9993 >BUG: 1242254 >Signed-off-by: Pranith Kumar K <pkarampu> >Reviewed-on: http://review.gluster.org/11639 >Reviewed-by: Raghavendra G <rgowdapp> >Tested-by: Gluster Build System <jenkins.com> >Reviewed-by: Xavier Hernandez <xhernandez> >Tested-by: NetBSD Build System <jenkins.org> BUG: 1243654 Change-Id: Iedb90d6a7d980fb88d6dfa6a6c978a165a4be3fd Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/11688 Reviewed-by: Xavier Hernandez <xhernandez> Tested-by: Gluster Build System <jenkins.com>
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.3, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/12078 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user