Description of problem: ----------------------- After the execution of 'gluster volume status' command, there was a error, " op_ctx modification failed" in glusterd log files Version-Release number of selected component (if applicable): ------------------------------------------------------------- glusterfs-3.5 Beta3 How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1. Create any type of volume 2. Start the volume 3. check, 'gluster volume status' command Actual results: --------------- There was an error, "op_ctx modification failed" in glusterd logs Expected results: ----------------- There should not be any errors in glusterd logs Additional info: ---------------- I ran this test on CentOS 6.5 [root@my-centos ~]# uname -r 2.6.32-431.5.1.el6.x86_64 [root@my-centos ~]# [root@my-centos ~]# cat /etc/issue CentOS release 6.5 (Final) Kernel \r on an \m Error messages in glusterd logs: <snip> [2014-02-18 15:04:18.119888] W [glusterd-op-sm.c:3404:glusterd_op_modify_op_ctx] 0-management: op_ctx modification failed [2014-02-18 15:04:18.122549] I [glusterd-handler.c:3530:__glusterd_handle_status_volume] 0-management: Received status volume req for volume distvol </snip>
Created attachment 864600 [details] glusterd log file Attached the glusterd log file
REVIEW: http://review.gluster.org/8337 (glusterd: Avoid spurious WARNING 'op_ctx modification failed') posted (#1) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/8337 (glusterd: Avoid spurious WARNING 'op_ctx modification failed') posted (#2) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/8337 (glusterd: Avoid spurious WARNING 'op_ctx modification failed') posted (#3) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/8337 (glusterd: Avoid spurious WARNING 'op_ctx modification failed') posted (#4) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/8337 (glusterd: Avoid spurious WARNING 'op_ctx modification failed') posted (#5) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/8337 (glusterd: Avoid spurious WARNING 'op_ctx modification failed') posted (#6) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/8337 (glusterd: Avoid spurious WARNING 'op_ctx modification failed') posted (#7) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/8337 (glusterd: Avoid spurious WARNING 'op_ctx modification failed') posted (#8) for review on master by Harshavardhana (harsha)
COMMIT: http://review.gluster.org/8337 committed in master by Krishnan Parthasarathi (kparthas) ------ commit 88eb28678c3a16264b5baa57af0d16778ea2c9e6 Author: Harshavardhana <harsha> Date: Sun Jul 20 14:59:42 2014 -0700 glusterd: Avoid spurious WARNING 'op_ctx modification failed' This patch fixes by wrapping this whole scenario and skips op_ctx modification for necessary commands. Change-Id: I3ecec19caefdc699d9a2dabfb456a89758ae4aa4 BUG: 1066529 Signed-off-by: Harshavardhana <harsha> Reviewed-on: http://review.gluster.org/8337 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Atin Mukherjee <amukherj> Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Krishnan Parthasarathi <kparthas>
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.0, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user