Bug 1025046 - Stop Volume Error - Staging Failed
Stop Volume Error - Staging Failed
Status: CLOSED EOL
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterfs (Show other bugs)
2.1
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Bug Updates Notification Mailing List
storage-qa-internal@redhat.com
glusterd
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-30 16:10 EDT by Matt Mahoney
Modified: 2015-12-03 12:14 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-12-03 12:14:54 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)
Volume stop error (3.33 MB, application/x-gzip)
2013-10-30 16:20 EDT, Matt Mahoney
no flags Details

  None (edit)
Description Matt Mahoney 2013-10-30 16:10:44 EDT
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:
Comment 1 Matt Mahoney 2013-10-30 16:20:03 EDT
Created attachment 817631 [details]
Volume stop error
Comment 3 Vivek Agarwal 2015-12-03 12:14:54 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.