Bug 1262417 - Data Tiering:Impossible to detach tier if hot tier has only one brick over a dist-rep cold tier volume
Data Tiering:Impossible to detach tier if hot tier has only one brick over a...
Status: CLOSED EOL
Product: GlusterFS
Classification: Community
Component: tiering (Show other bugs)
3.7.4
Unspecified Unspecified
high Severity urgent
: ---
: ---
Assigned To: Mohammed Rafi KC
bugs@gluster.org
:
Depends On:
Blocks: 1260923
  Show dependency treegraph
 
Reported: 2015-09-11 11:17 EDT by nchilaka
Modified: 2017-03-08 05:49 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-03-08 05:49:21 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)

  None (edit)
Description nchilaka 2015-09-11 11:17:27 EDT
Description of problem:
========================
it is impossible to detach a tier on  a single hot brick in hot tier over a dist-rep cold tier(non-empty)(see steps)
[root@zod glusterfs]# gluster  v detach-tier zx status
volume detach-tier status: failed: Detach-tiernot started
[root@zod glusterfs]# gluster  v detach-tier zx start
volume detach-tier start: failed: Bricks not from same subvol for distribute
[root@zod glusterfs]# gluster  v detach-tier zx start
volume detach-tier start: failed: Bricks not from same subvol for distribute
[root@zod glusterfs]# gluster  v detach-tier zx commit
volume detach-tier commit: failed: Bricks not from same subvol for distribute
[root@zod glusterfs]# gluster  v detach-tier zx commit force
volume detach-tier commit force: failed: Bricks not from same subvol for distribute

Version-Release number of selected component (if applicable):
================================================================
[root@zod ~]# rpm -qa|grep gluster
glusterfs-client-xlators-3.7.4-0.27.git143f0f9.el7.centos.x86_64
glusterfs-cli-3.7.4-0.27.git143f0f9.el7.centos.x86_64
glusterfs-libs-3.7.4-0.27.git143f0f9.el7.centos.x86_64
glusterfs-api-3.7.4-0.27.git143f0f9.el7.centos.x86_64
glusterfs-fuse-3.7.4-0.27.git143f0f9.el7.centos.x86_64
glusterfs-debuginfo-3.7.4-0.27.git143f0f9.el7.centos.x86_64
glusterfs-server-3.7.4-0.27.git143f0f9.el7.centos.x86_64
glusterfs-3.7.4-0.27.git143f0f9.el7.centos.x86_64
[root@zod ~]# gluster --version
glusterfs 3.7.4 built on Sep  9 2015 01:30:47
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.
[root@zod ~]# 



Steps to Reproduce:
==================
1.create a dist-rep volume and mount it on fuse and create some files
2) Now attach a tier with only one brick
3)now issue a detach tier
it is impossible to detach due to following error






[root@zod glusterfs]# gluster v info zx
 
Volume Name: zx
Type: Tier
Volume ID: f001c58b-82a6-4880-a254-4e3f09a191d3
Status: Started
Number of Bricks: 5
Transport-type: tcp
Hot Tier :
Hot Tier Type : Distribute
Number of Bricks: 1
Brick1: zod:/rhs/brick4/zx
Cold Tier:
Cold Tier Type : Distributed-Replicate
Number of Bricks: 2 x 2 = 4
Brick2: zod:/rhs/brick1/zx
Brick3: yarrow:/rhs/brick1/zx
Brick4: zod:/rhs/brick2/zx
Brick5: yarrow:/rhs/brick2/zx
Options Reconfigured:
performance.readdir-ahead: on
[root@zod glusterfs]# gluster v status zx
Status of volume: zx
Gluster process                             TCP Port  RDMA Port  Online  Pid
------------------------------------------------------------------------------
Hot Bricks:
Brick zod:/rhs/brick4/zx                    49180     0          Y       2083 
Cold Bricks:
Brick zod:/rhs/brick1/zx                    49178     0          Y       1968 
Brick yarrow:/rhs/brick1/zx                 49172     0          Y       17259
Brick zod:/rhs/brick2/zx                    49179     0          Y       1986 
Brick yarrow:/rhs/brick2/zx                 49173     0          Y       17279
NFS Server on localhost                     2049      0          Y       2106 
NFS Server on yarrow                        2049      0          Y       17455
 
Task Status of Volume zx
------------------------------------------------------------------------------
Task                 : Rebalance           
ID                   : 0ffd667b-9810-4b17-80f0-454dd457b39e
Status               : in progress         
 
[root@zod glusterfs]# gluster  v detach-tier zx status
volume detach-tier status: failed: Detach-tiernot started
[root@zod glusterfs]# gluster  v detach-tier zx start
volume detach-tier start: failed: Bricks not from same subvol for distribute
[root@zod glusterfs]# gluster  v detach-tier zx start
volume detach-tier start: failed: Bricks not from same subvol for distribute
[root@zod glusterfs]# gluster  v detach-tier zx commit
volume detach-tier commit: failed: Bricks not from same subvol for distribute
[root@zod glusterfs]# gluster  v detach-tier zx commit force
volume detach-tier commit force: failed: Bricks not from same subvol for distribute
[root@zod glusterfs]# 



logs are attached
Comment 1 nchilaka 2015-09-11 11:23:36 EDT
sosreports

[root@rhsqe-repo sosreports]# chmod -R 0777 bug.1262417
[root@rhsqe-repo sosreports]# pwd
/home/repo/sosreports
[root@rhsqe-repo sosreports]# hostname
rhsqe-repo.lab.eng.blr.redhat.com
[root@rhsqe-repo sosreports]# ll bug.1262417
total 8
drwxrwsrwx. 2 root qe 4096 Sep 11 20:46 node1
drwxrwsrwx. 2 root qe 4096 Sep 11 20:46 node2
Comment 2 Kaushal 2017-03-08 05:49:21 EST
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.

Note You need to log in before you can comment on or make changes to this bug.