Bug 999968 - If all the bricks of a volume are started with valgrind, gluster volume stop just returns after timeout without stopping the volume.
If all the bricks of a volume are started with valgrind, gluster volume stop ...
Status: CLOSED EOL
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterd (Show other bugs)
2.1
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Bug Updates Notification Mailing List
storage-qa-internal@redhat.com
glusterd
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-22 09:17 EDT by Vijaykumar Koppad
Modified: 2015-12-03 12:19 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-12-03 12:19:55 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Vijaykumar Koppad 2013-08-22 09:17:33 EDT
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-3.4.0.21rhs-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. 


Additional info:
Comment 3 Vivek Agarwal 2015-12-03 12:19:55 EST
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.

Note You need to log in before you can comment on or make changes to this bug.