Bug 1214387

Summary:	Incorrect vol info post detach on disperse volume
Product:	[Community] GlusterFS	Reporter:	Anoop <annair>
Component:	tiering	Assignee:	Mohammed Rafi KC <rkavunga>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	medium	Docs Contact:
Priority:	urgent
Version:	mainline	CC:	bugs, nchilaka, sankarshan
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-4.1.4	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1229257 (view as bug list)		Environment:
Last Closed:	2018-10-08 09:52:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1229257, 1260923

Description Anoop 2015-04-22 15:33:13 UTC

Description of problem:
Detach tier from a disperse  volume (cold) is giving messing up the disperse vol info

Version-Release number of selected component (if applicable):
glusterfs-server-3.7dev-0.994.git0d36d4f.el6.x86_64

How reproducible:


Steps to Reproduce:
1. Create a simple disperse volume [ 1 x (4+2)]
2. Attach a tier (replica) to the volume
3. Now, detach the tier. 
4. This is what the vol info shows post the detach:
[root@dhcp35-56 ~]# gluster vol info
 
Volume Name: vol2
Type: Distributed-Disperse
Volume ID: b267ba15-82df-4842-bd41-ac233592d5ba
Status: Created
Number of Bricks: 3 x (4 + 2) = 6
Transport-type: tcp
Bricks:
Brick1: 10.70.35.56:/rhs/brick1
Brick2: 10.70.35.67:/rhs/brick1
Brick3: 10.70.35.56:/rhs/brick2
Brick4: 10.70.35.67:/rhs/brick2
Brick5: 10.70.35.56:/rhs/brick3
Brick6: 10.70.35.67:/rhs/brick3

The volume now is shown up as "Distributed-Disperse" and the distribute count is for some reason 3.

Comment 1 Dan Lambright 2015-04-22 17:13:39 UTC

I believe this was called out and fixed in a separate bug. Assigning to Rafi to see..

Comment 2 Mohammed Rafi KC 2015-04-23 05:25:51 UTC

upstream patch : http://review.gluster.org/#/c/10339/

Comment 3 Niels de Vos 2015-05-15 13:07:25 UTC

This change should not be in "ON_QA", the patch posted for this bug is only available in the master branch and not in a release yet. Moving back to MODIFIED until there is an beta release for the next GlusterFS version.

Comment 4 Amar Tumballi 2018-10-08 09:52:08 UTC

This bug was ON_QA status, and on GlusterFS product in bugzilla, we don't have that as a valid status. We are closing it as 'CURRENT RELEASE ' to indicate the availability of the fix, please reopen if found again.