Description of problem: Hi Pranith, I see a lot of these messages in nfs.log. [2016-01-20 12:15:45.595207] E [ec-common.c:1945:__ec_manager] (-->/usr/lib64/glusterfs/3.7.5/xlator/cluster/distribute.so(dht_access+0x177) [0x7f6e09f39f67] -->/usr/lib64/glusterfs/3.7.5/xlator/cluster/disperse.so(ec_gf_access+0x2c) [0x7f6e0a168a1c] -->/usr/lib64/glusterfs/3.7.5/xlator/cluster/disperse.so(__ec_manager+0x166) [0x7f6e0a16e5d6] ) 0-: Assertion failed: fop->state >= 0 [2016-01-20 12:15:45.595411] E [ec-common.c:1945:__ec_manager] (-->/usr/lib64/glusterfs/3.7.5/xlator/cluster/distribute.so(dht_access+0x177) [0x7f6e09f39f67] -->/usr/lib64/glusterfs/3.7.5/xlator/cluster/disperse.so(ec_gf_access+0x2c) [0x7f6e0a168a1c] -->/usr/lib64/glusterfs/3.7.5/xlator/cluster/disperse.so(__ec_manager+0x166) [0x7f6e0a16e5d6] ) 0-: Assertion failed: fop->state >= 0 [root@transformers ~]# grep -i "fop->state >= 0" /var/log/glusterfs/nfs.log |wc -l 222918 -Bhaskar Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/13278 (cluster/ec: Never return -ve state) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/13278 (cluster/ec: Never return -ve state) posted (#2) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/13278 (cluster/ec: Never return -ve state) posted (#3) for review on master by Xavier Hernandez (xhernandez)
COMMIT: http://review.gluster.org/13278 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit 95597b87e32b8615ca63f8b0b3bb8d488272d95d Author: Pranith Kumar K <pkarampu> Date: Fri Jan 22 12:11:40 2016 +0530 cluster/ec: Never return -ve state Ec manager shouldn't return -ve states, but it is, fixed that. Change-Id: I3f97c6ba2dbf9da724e8e1ee9b2c9da73f40013d BUG: 1300929 Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/13278 Tested-by: Xavier Hernandez <xhernandez> Smoke: Gluster Build System <jenkins.com> CentOS-regression: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD 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.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