[Bugs] [Bug 1207238] New: data tiering:force Remove brick is detaching-tier
bugzilla at redhat.com
bugzilla at redhat.com
Mon Mar 30 13:36:29 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1207238
Bug ID: 1207238
Summary: data tiering:force Remove brick is detaching-tier
Product: GlusterFS
Version: mainline
Component: cli
Severity: urgent
Assignee: bugs at gluster.org
Reporter: nchilaka at redhat.com
CC: bugs at gluster.org, gluster-bugs at redhat.com
Description of problem:
=======================
In a tiered volume,removing a brick fails.
So if we try force remove-brick , either on cold or hot, it just goes and
detaches tier. This is a serious bug
Version-Release number of selected component (if applicable):
============================================================
3.7 upstream nightlies build
http://download.gluster.org/pub/gluster/glusterfs/nightly/glusterfs/epel-6-x86_64/glusterfs-3.7dev-0.821.git0934432.autobuild//
root at interstellar glusterfs]# gluster --version
glusterfs 3.7dev built on Mar 28 2015 01:05:28
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GlusterFS under the terms of the GNU General
Public License.
How reproducible:
=================
Easy to reproduce
Steps to Reproduce:
==================
1.create a gluster volume(i created a distribute type) and start the volume and
attach a tier to the volume using attach-tier
2.Now do a remove-brick and use force option as below
gluster v remove-brick voly transformers:/pavanbrick2/voly/hb1 force
Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y
volume remove-brick commit force: success
3. This forcefully just detaches tier instead of the brick
Expected results:
================
remove a brick should not remove the tier
Additional info(CLI logs):
=========================
[root at interstellar glusterfs]# gluster v create voly
interstellar:/pavanbrick1/voly/b1 transformers:/pavanbrick1/voly/b1
volume create: voly: success: please start the volume to access data
[root at interstellar glusterfs]# gluster v start voly
volume start: voly: success
[root at interstellar glusterfs]# gluster v info voly
Volume Name: voly
Type: Distribute
Volume ID: 22412494-df85-4458-a80f-0e4c0cc76572
Status: Started
Number of Bricks: 2
Transport-type: tcp
Bricks:
Brick1: interstellar:/pavanbrick1/voly/b1
Brick2: transformers:/pavanbrick1/voly/b1
[root at interstellar glusterfs]# gluster v status voly
Status of volume: voly
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
Brick interstellar:/pavanbrick1/voly/b1 49158 0 Y 27482
Brick transformers:/pavanbrick1/voly/b1 49158 0 Y 31954
NFS Server on localhost N/A N/A N N/A
NFS Server on 10.70.34.44 N/A N/A N N/A
Task Status of Volume voly
------------------------------------------------------------------------------
There are no active volume tasks
[root at interstellar glusterfs]# gluster v attach-tier voly
interstellar:/pavanbrick2/voly/hb1 transformers:/pavanbrick2/voly/hb1
volume add-brick: success
[root at interstellar glusterfs]# gluster v info voly
Volume Name: voly
Type: Tier
Volume ID: 22412494-df85-4458-a80f-0e4c0cc76572
Status: Started
Number of Bricks: 4 x 1 = 4
Transport-type: tcp
Bricks:
Brick1: transformers:/pavanbrick2/voly/hb1
Brick2: interstellar:/pavanbrick2/voly/hb1
Brick3: interstellar:/pavanbrick1/voly/b1
Brick4: transformers:/pavanbrick1/voly/b1
[root at interstellar glusterfs]# gluster v status voly
Status of volume: voly
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
Brick transformers:/pavanbrick2/voly/hb1 49159 0 Y 32013
Brick interstellar:/pavanbrick2/voly/hb1 49159 0 Y 27567
Brick interstellar:/pavanbrick1/voly/b1 49158 0 Y 27482
Brick transformers:/pavanbrick1/voly/b1 49158 0 Y 31954
NFS Server on localhost N/A N/A N N/A
NFS Server on 10.70.34.44 N/A N/A N N/A
Task Status of Volume voly
------------------------------------------------------------------------------
There are no active volume tasks
[root at interstellar glusterfs]# gluster v remove-brick voly
transformers:/pavanbrick2/voly/hb1 force
Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y
volume remove-brick commit force: success
[root at interstellar glusterfs]# gluster v status voly
Status of volume: voly
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
Brick interstellar:/pavanbrick1/voly/b1 49158 0 Y 27482
Brick transformers:/pavanbrick1/voly/b1 49158 0 Y 31954
NFS Server on localhost N/A N/A N N/A
NFS Server on 10.70.34.44 N/A N/A N N/A
Task Status of Volume voly
------------------------------------------------------------------------------
There are no active volume tasks
[root at interstellar glusterfs]# gluster v info voly
Volume Name: voly
Type: Tier
Volume ID: 22412494-df85-4458-a80f-0e4c0cc76572
Status: Started
Number of Bricks: 2 x 1 = 2
Transport-type: tcp
Bricks:
Brick1: interstellar:/pavanbrick1/voly/b1
Brick2: transformers:/pavanbrick1/voly/b1
[root at interstellar glusterfs]#
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list