Hide Forgot
Description of problem: While starting/stopping volume that comprised of 64 RHS hots with one brick on each host: Volume stop resulted in the following error: time -p gluster volume stop 64Servers_64Bricks Stopping volume will make its data inaccessible. Do you want to continue? (y/n) y volume stop: 64Servers_64Bricks: failed: Staging failed on 10.16.159.60. Error: Volume 64Servers_64Bricks is not in the started state Volume is shown to be in Started state: gluster> volume info 64Servers_64Bricks Volume Name: 64Servers_64Bricks Type: Distribute Volume ID: b7868f5a-aaaf-46b3-87a8-b4a45e27ce7c Status: Started Number of Bricks: 64 Version-Release number of selected component (if applicable): Big Bend How reproducible: Repeatable - start/stop iteratively several times. Steps to Reproduce: 1. Create volume with 64 servers and one brick on each server Repeat the following several times, until error occurs 2. Volume start 3. Volume start Actual results: Volume fails to be stopped Work around is to "service glusterd restart" Expected results: Additional info:
Created attachment 817631 [details] Volume stop 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.