Bug 763669 (GLUSTER-1937) - Reinitialize disk doesn't stop running volume and still has older entries
Summary: Reinitialize disk doesn't stop running volume and still has older entries
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-1937
Product: GlusterSP
Classification: Retired
Component: core
Version: 3.1.0
Hardware: All
OS: Linux
urgent
high
Target Milestone: 3.1.1
Assignee: Balamurugan Arumugam
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-12 20:50 UTC by Harshavardhana
Modified: 2015-03-23 01:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Reinitialize Button (119.52 KB, image/png)
2010-10-12 17:50 UTC, Harshavardhana 		no flags Details
Erasing disk doesn't give any warning if it has existing data (119.63 KB, image/png)
2010-10-12 17:51 UTC, Harshavardhana 		no flags Details
Volume start doesn't start and forceful start is hung (84.29 KB, image/png)
2010-10-12 17:53 UTC, Harshavardhana 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Harshavardhana 2010-10-12 17:51:11 UTC 
Created attachment 350
Comment 1 Harshavardhana 2010-10-12 17:53:20 UTC 
Created attachment 351
Comment 2 Harshavardhana 2010-10-12 17:55:12 UTC 
(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>
Comment 3 Harshavardhana 2010-10-12 20:50:02 UTC 
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 ~]#
Note You need to log in before you can comment on or make changes to this bug.