Red Hat Bugzilla – Bug 999968
If all the bricks of a volume are started with valgrind, gluster volume stop just returns after timeout without stopping the volume.
Last modified: 2015-12-03 12:19:55 EST
Description of problem: If all the bricks of volume are started with valgrind, the
the gluster volume stop just returns to prompt without actually stopping the volume. gluster volume status also says all the bricks as up .
If the volume stop fails, it should at least give some error.
Version-Release number of selected component (if applicable):glusterfs-188.8.131.52rhs-1.el6rhs.x86_64
How reproducible:Happens everytime
Steps to Reproduce:
1.kill running glusterd and start it as " glusterd --xlator-option *.run-with-valgrind=yes"
2.killall glusterfsd and gluster volume start <VOLNAME> force.
3.then try to stop the volume
Actual results:It just returns to prompt without actually stopping the volume
Expected results:It should stop the volume and if it fails , at least it should give some error.
Thank you for submitting this issue for consideration in Red Hat Gluster Storage. The release for which you requested us to review, is now End of Life. Please See https://access.redhat.com/support/policy/updates/rhs/
If you can reproduce this bug against a currently maintained version of Red Hat Gluster Storage, please feel free to file a new report against the current release.