| Summary: | Reinitialize disk doesn't stop running volume and still has older entries | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] GlusterSP | Reporter: | Harshavardhana <fharshav> | ||||||||
| Component: | core | Assignee: | Balamurugan Arumugam <bala> | ||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | urgent | ||||||||||
| Version: | 3.1.0 | CC: | cww, platform | ||||||||
| Target Milestone: | 3.1.1 | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | All | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | Type: | --- | |||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
|
Description
Harshavardhana
2010-10-12 17:51:11 UTC
Created attachment 351 (In reply to comment #2) > Created an attachment (id=351) [details] > Volume start doesn't start and forceful start is hung After all this stop and start a volume just hoses everything. 2010-10-12 20:52:16.375425: Send: <command request="start-volume" id="mmFYg2n15834" version="3.1.0" ><volume-name>jacobtest1</volume-name><force>yes</force></command> 2010-10-12 20:52:16.426579: Receive: <?xml version="1.0" ?><command id="mmFYg2n15834" response="start-volume" response-code="Error starting volume service" version="3.1.0"><volume-name>jacobtest1</volume-name></command> Now that webUI gives an option to reinitialize the disk, there is no possibility of stopping and starting the volume. This leads to dangling volume information. Why do you have that weird Reinitialize button?, it should throw a big warning if its being used when a user tries to initialize it? If a user reinitializes and volume is not stopped and restarted with additional config change. [root@jacobgsp310 ~]# gluster volume info Volume Name: jacobtest1 Type: Distributed-Replicate Status: Started Number of Bricks: 2 x 2 = 4 Transport-type: tcp Bricks: Brick1: jacobgsp310:/data/6fdad7b5-fbce-4dbc-9e33-1c7ab0e1cccd/8e1fa7ec-803a-46be-b3cf-fc7e699ffec0/exports/brick1 Brick2: jacobgsp310:/data/e324b4aa-233b-4692-8a3d-fa4919ced7b7/8e1fa7ec-803a-46be-b3cf-fc7e699ffec0/exports/brick1 Brick3: jacobgsp310:/data/fcf9561c-1a46-4b75-ae8e-2c268808ab43/8e1fa7ec-803a-46be-b3cf-fc7e699ffec0/exports/brick1 Brick4: jacobgsp310:/data/240e50d2-6742-4038-9b56-0e00ed30d443/8e1fa7ec-803a-46be-b3cf-fc7e699ffec0/exports/brick1 Options Reconfigured: auth.allow: *,10.1.30.117 [root@jacobgsp310 ~]# |