glusterfs.git/cli/src, branch v3.7.0beta2

glusterd/tiering : cksum mismatch for tiered volume

2015-05-10T16:43:03+00:00

        Back port of http://review.gluster.org/#/c/10406

Once we updated the volinfo from orginator node, the hot
type was overwritten with volume type.

Then the same dictionary was sent to peer node to perform
the commit of attach-tier, that will cause hot type to
replace with volume type, eventually end up in cksum
mismatch

Change-Id: I402dceb4d672d0b3a7b91a92f52c1057050dbedc
BUG: 1219845
Signed-off-by: Mohammed Rafi KC 
Reviewed-on: http://review.gluster.org/10677
Reviewed-by: Niels de Vos 
Tested-by: NetBSD Build System
Tested-by: Gluster Build System

tiering: Send both attach-tier and tier-start together

2015-05-10T04:51:36+00:00

        Back port of http://review.gluster.org/10363

After attaching tier, we have to start tier rebalance process.
This patch is to trigger tier start along with attch-tier.

>Change-Id: I39380f95123f0087a82213ef263f9f33adcc5adc
>BUG: 1214222
>Signed-off-by: Mohammed Rafi KC 
>Reviewed-on: http://review.gluster.org/10363
>Tested-by: Gluster Build System 
>Reviewed-by: Dan Lambright 

Change-Id: Ia27e97a9dc0772f3f56b991ce4019281ab7bf1b5
BUG: 1219848
Signed-off-by: Mohammed Rafi KC 
Reviewed-on: http://review.gluster.org/10711
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System
Reviewed-by: Vijay Bellur

cli/tiering: volume info should display details about tier

2015-05-10T04:50:45+00:00

        Back port of http://review.gluster.org/#/c/10339/

>> gluster volume info patchy

Volume Name: patchy
Type: Tier
Volume ID: 8bf1a1ca-6417-484f-821f-18973a7502a8
Status: Created
Number of Bricks: 8
Transport-type: tcp
Hot Tier :
Hot Tier Type : Replicate
Number of Bricks: 1 x 2 = 2
Brick1: hostname:/home/brick30
Brick2: hostname:/home/brick31
Cold Bricks:
Cold Tier Type : Disperse
Number of Bricks: 1 x (4 + 2) = 6
Brick3: hostname:/home/brick20
Brick4: hostname:/home/brick21
Brick5: hostname:/home/brick23
Brick6: hostname:/home/brick24
Brick7: hostname:/home/brick25
Brick8: hostname:/home/brick26

Change-Id: I7b9025af81263ebecd641b4b6897b20db8b67195
BUG: 1219842
Signed-off-by: Mohammed Rafi KC 
Reviewed-on: http://review.gluster.org/10676
Reviewed-by: Dan Lambright 
Tested-by: NetBSD Build System
Tested-by: Gluster Build System

cli/tiering: display hot tier, and cold tier separately

2015-05-10T04:26:21+00:00

        back port of http://review.gluster.org/#/c/10328

cli commands display the brick information without a way
to distinguish hot tier, and cold tier.

This patch will change all the cli related output, without
changing the corresponding xml output.

This patch will change following things
>> gluster volume info
Volume Name: patchy
Type: Tier
Volume ID: 7745d367-811a-4fe9-a500-d04e7afa94bf
Status: Created
Number of Bricks: 3 x 2 = 6
Transport-type: tcp
Hot Bricks:
Brick1: hostname:/home/brick21
Brick2: hostname:/home/brick20
Cold Bricks:
Brick3: hostname:/home/brick19
Brick4: hostname:/home/brick16
Brick5: hostname:/home/brick17
Brick6: hostname:/home/brick18

>>gluster volume status

Status of volume: patchy
Gluster process                             TCP Port  RDMA Port  Online
Pid
------------------------------------------------------------------------------
Hot Bricks:
Brick hostname:/home/brick21              49152     0          Y
4690
Brick hostname:/home/brick20              49153     0          Y
4707
Cold Bricks:
Brick hostname:/home/brick19              49154     0          Y
4724
Brick hostname:/home/brick16              49155     0          Y
4741
Brick hostname:/home/brick17              49156     0          Y
4758
Brick hostname:/home/brick18              49157     0          Y
4775
NFS Server on localhost                     2049      0          Y
4793

Task Status of Volume patchy
------------------------------------------------------------------------------
There are no active volume tasks

>>gluster volume status pathy detail

Status of volume: patchy
Hot Bricks:
------------------------------------------------------------------------------
Brick                : Brick hostname:/home/brick21
TCP Port             : 49162
RDMA Port            : 0
Online               : Y
Pid                  : 22677
File System          : ext4
Device               :
/dev/mapper/luks-cd077c56-42ba-44b1-8195-f214b9bc990c
Mount Options        : rw,seclabel,relatime,data=ordered
Inode Size           : 256
Disk Space Free      : 127.3GB
Total Disk Space     : 165.4GB
Inode Count          : 11026432
Free Inodes          : 10998043
------------------------------------------------------------------------------
Brick                : Brick hostname:/home/brick20
TCP Port             : 49161
RDMA Port            : 0
Online               : Y
Pid                  : 22660
File System          : ext4
Device               :
/dev/mapper/luks-cd077c56-42ba-44b1-8195-f214b9bc990c
Mount Options        : rw,seclabel,relatime,data=ordered
Inode Size           : 256
Disk Space Free      : 127.3GB
Total Disk Space     : 165.4GB
Inode Count          : 11026432
Free Inodes          : 10998043
Cold Bricks:
------------------------------------------------------------------------------
Brick                : Brick hostname:/home/brick19
TCP Port             : 49157
RDMA Port            : 0
Online               : Y
Pid                  : 22501
File System          : ext4
Device               :
/dev/mapper/luks-cd077c56-42ba-44b1-8195-f214b9bc990c
Mount Options        : rw,seclabel,relatime,data=ordered
Inode Size           : 256
Disk Space Free      : 127.3GB
Total Disk Space     : 165.4GB
Inode Count          : 11026432
Free Inodes          : 10998043
------------------------------------------------------------------------------
Brick                : Brick hostname:/home/brick16
TCP Port             : 49158
RDMA Port            : 0
Online               : Y
Pid                  : 22518
File System          : ext4
Device               :
/dev/mapper/luks-cd077c56-42ba-44b1-8195-f214b9bc990c
Mount Options        : rw,seclabel,relatime,data=ordered
Inode Size           : 256
Disk Space Free      : 127.3GB
Total Disk Space     : 165.4GB
Inode Count          : 11026432
Free Inodes          : 10998043
------------------------------------------------------------------------------
Brick                : Brick hostname:/home/brick17
TCP Port             : 49159
RDMA Port            : 0
Online               : Y
Pid                  : 22535
File System          : ext4
Device               :
/dev/mapper/luks-cd077c56-42ba-44b1-8195-f214b9bc990c
Mount Options        : rw,seclabel,relatime,data=ordered
Inode Size           : 256
Disk Space Free      : 127.3GB
Total Disk Space     : 165.4GB
Inode Count          : 11026432
Free Inodes          : 10998043
------------------------------------------------------------------------------
Brick                : Brick hostname:/home/brick18
TCP Port             : 49160
RDMA Port            : 0
Online               : Y
Pid                  : 22552
File System          : ext4
Device               :
/dev/mapper/luks-cd077c56-42ba-44b1-8195-f214b9bc990c
Mount Options        : rw,seclabel,relatime,data=ordered
Inode Size           : 256
Disk Space Free      : 127.3GB
Total Disk Space     : 165.4GB
Inode Count          : 11026432
Free Inodes          : 10998043

Change-Id: I7d584eb8782129c12876cce2ba8ffba6c0a620bd
BUG: 1219842
Signed-off-by: Mohammed Rafi KC 
Reviewed-on: http://review.gluster.org/10675
Reviewed-by: Dan Lambright 
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System
Reviewed-by: Krishnan Parthasarathi 
Tested-by: Krishnan Parthasarathi

tiering/cli: Check replica count and bricks are proper or not

2015-05-10T03:25:13+00:00

        Back port of http://review.gluster.org/10428

Right now, attach-tier calls parsing function for add-brick.
Add-brick does not have any check for brick count and replca
count compatibility.

>Change-Id: I44ec13eadffc003a9ebf8c4eb0193df559933a68
>BUG: 1215122
>Signed-off-by: Mohammed Rafi KC 
>Reviewed-on: http://review.gluster.org/10428
>Reviewed-by: Dan Lambright 
>Tested-by: Gluster Build System 
>Reviewed-by: Vijay Bellur 

Change-Id: Ie86d5b61b044386a062bfc9782178853e3af0f11
BUG: 1219850
Signed-off-by: Mohammed Rafi KC 
Reviewed-on: http://review.gluster.org/10710
Reviewed-by: Dan Lambright 
Tested-by: Gluster Build System

cli/tiering: Enhance cli output for tiering

2015-05-09T17:26:36+00:00

        back port of http://review.gluster.org/10284

Fix for handling cli output for attach-tier and
detach-tier

>Change-Id: I4d17f4b09612754fe1b8cec6c2e14927029b9678
>BUG: 1211562
>Signed-off-by: Mohammed Rafi KC 
>Reviewed-on: http://review.gluster.org/10284
>Reviewed-by: Dan Lambright 
>Tested-by: Gluster Build System 
>Tested-by: NetBSD Build System
>Reviewed-by: Vijay Bellur 

Change-Id: Ic30c8f0a104d89bf98f5d0069937a34674ee3f2d
BUG: 1220052
Signed-off-by: Mohammed Rafi KC 
Reviewed-on: http://review.gluster.org/10713
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

cli/tiering : Parse detach-tier command properly

2015-05-09T17:13:03+00:00

        Back port of http://review.gluster.org/10303

gluster detach-tier help should show the usage of
detach-tier command properly.

Also, instead of force option, if any other was given,
then the command should fail with a usage message

>Change-Id: Ie801529176db067c98fd1bfada056cbc647973fb
>BUG: 1211570
>Signed-off-by: Mohammed Rafi KC 
>Reviewed-on: http://review.gluster.org/10303
>Tested-by: NetBSD Build System
>Tested-by: Gluster Build System 
>Reviewed-by: Atin Mukherjee 
>Reviewed-by: Dan Lambright 

Change-Id: I51ef7c3450c219b2b24724592270461570436010
BUG: 1220050
Signed-off-by: Mohammed Rafi KC 
Reviewed-on: http://review.gluster.org/10709
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd: support for tier volumes 'detach start' and 'detach commit'

2015-05-09T15:35:14+00:00

        Back port of http://review.gluster.org/10108

These commands work in a manner analagous to rebalancing when removing a
brick. The existing migration daemon detects "detach start" and switches
to moving data off the hot tier. While in this state all lookups are
directed to the cold tier.

gluster v detach-tier  start
gluster v detach-tier  commit

The status and stop cli commands shall be submitted separately.

>Change-Id: I24fda5cc3ba74f5fb8aa9a3234ad51f18b80a8a0
>BUG: 1205540
>Signed-off-by: Dan Lambright 
>Signed-off-by: root 
>Signed-off-by: Dan Lambright 
>Reviewed-on: http://review.gluster.org/10108
>Reviewed-by: Kaleb KEITHLEY 

Change-Id: I212d748d077fb5870ee84b316c653acbafbea3f7
BUG: 1220047
Signed-off-by: Mohammed Rafi KC 
Reviewed-on: http://review.gluster.org/10708
Reviewed-by: Dan Lambright 
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

cli: Error out when there is not enough memory

2015-05-09T07:31:57+00:00

Change-Id: Ia8d061de5be1343cc10a945f6cf011686a770d33
BUG: 1220020
Signed-off-by: Humble Devassy Chirammal 
Reviewed-on: http://review.gluster.org/10144
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System
Reviewed-by: Vijay Bellur  
(cherry picked from commit f6e24fc54453669f3943e50f44cce9bb6070a71a)
Reviewed-on: http://review.gluster.org/10674
Reviewed-by: Kaushal M 
Tested-by: Kaushal M

quota/marker: turn off inode quotas by default

2015-05-08T12:42:20+00:00

inode quota is a new feature implemented in glusterfs-3.7
if quota is enabled in the older version and is upgraded
to a new version, we can hit setxattr spike during self-heal
of inode quotas. So, when a quota is enabled, turn off
inode-quotas with a xlator option.

With this patch, we still account for inode quotas but only
when a write operation is performed for a particular file.
User will be able to query inode quotas once the Inode-quota
xlator option is enabled.

Change-Id: I52fb28bf7024989ce7bb08ac63a303bf3ec1ec9a
BUG: 1218243
Signed-off-by: vmallika 
Signed-off-by: Sachin Pandit 
Reviewed-on: http://review.gluster.org/10152
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur 
Signed-off-by: Sachin Pandit 
Reviewed-on: http://review.gluster.org/10621