glusterfs.git/cli, branch v3.7.11

quota/cli: display quota usage on path when limit not set

2016-04-05T12:27:21+00:00

This is a backport of http://review.gluster.org/#/c/13893/

When a quota limit is not set, 'quota list ' should still display
the usage when a path parameter is specified.

> Change-Id: Ida12d9c5e348fbd98db4d68d9324c623cbdd3dea
> BUG: 1323360
> Signed-off-by: vmallika 

Change-Id: I51cf46faffb324d2632dfde4264cd95d2da22479
BUG: 1323490
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/13895
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Smoke: Gluster Build System

afr: add mtime based split-brain resolution to CLI

2016-04-04T17:33:56+00:00

Backport of http://review.gluster.org/#/c/13828/

Extended the CLI to include support for split-brain resolution based on
mtime. The command syntax is:

$:gluster volume heal  split-brain latest-mtime 

where  can be either the full file name as seen from the root of the
volume (or) the gfid-string representation of the file.

Change-Id: I7a16f72ff1a4495aa69f43f22758a9404e958b4f
BUG: 1321748
Signed-off-by: Ravishankar N 
Reviewed-on: http://review.gluster.org/13838
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Anuradha Talur 
CentOS-regression: Gluster Build System 
Reviewed-by: Pranith Kumar Karampuri

cli: Do not remove whitespace if key is user.* in volume set

2016-03-24T09:23:16+00:00

Backport of http://review.gluster.org/#/c/13669

setting any user.* option can have multiple words in the key and hence skip the
process of trimming whitespaces.

Change-Id: Ia295428d7cda55e5470fef668325bea497f2333d
BUG: 1320821
Signed-off-by: Atin Mukherjee 
Reviewed-on: http://review.gluster.org/13669
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Kaushal M 
Reviewed-on: http://review.gluster.org/13821

Tier: displaying status only one the nodes running tierd

2016-03-22T09:07:34+00:00

        back-port of : http://review.gluster.org/#/c/13647/2

When tier status is given on a cluster where one node doesn't
have tierd running, the status is shown as not started.

The status of the node without tierd should not be displayed.

This patch will skip if the current node if the status is not
started

>Change-Id: Ibeb39f13133f94a5869b020c5ccd9bd6992323f1
>BUG: 1315666
>Signed-off-by: hari gowtham 

Change-Id: I15399db6bcdea68c0a7bebcf113329d37def6e1d
BUG: 1316808
Signed-off-by: hari gowtham 
Reviewed-on: http://review.gluster.org/13676
Smoke: Gluster Build System 
Tested-by: hari gowtham 
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Dan Lambright

Cli/tier: separating services from cold bricks in xml

2016-03-22T09:05:57+00:00

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

fix: The cold bricks tag included the processes also.
The patch has removed the processes from being mentioned
inside the cold brick tag and are mentioned below by
closing the cold brick tag after the brick count.

Previous output:
        
          
            192.168.1.102
            /data/gluster/b3
            8c088528-e1aee3b2b40f
            1
            49157
            
              49157
              N/A
            
            1160
          
          
            NFS Server
            localhost
            8c088528-e1aee3b2b40f
            0
            N/A
            
              N/A
              N/A
            
            -1
          
        

Expected output:
        
          
            192.168.1.102
            /data/gluster/b3
            8c088528-e1aee3b2b40f
            1
            49157
            
              49157
              N/A
            
            1160
          
        
        
          NFS Server
          localhost
          8c088528-e1aee3b2b40f
          0
          N/A
          
            N/A
            N/A
          
          -1
        

>Change-Id: Ieccd017d7b2edb16786323f1a76402f020bdfb0d
>BUG: 1294497
>Signed-off-by: hari 
>Reviewed-on: http://review.gluster.org/13101
>Smoke: Gluster Build System 
>Tested-by: hari gowtham 
>NetBSD-regression: NetBSD Build System 
>CentOS-regression: Gluster Build System 
>Reviewed-by: Dan Lambright 

Change-Id: Ia207b4f8140c7a449ca3e3e2c90e5f69dac88d57
BUG: 1318505
Signed-off-by: hari 
Reviewed-on: http://review.gluster.org/13757
Smoke: Gluster Build System 
Tested-by: hari gowtham 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Dan Lambright

snapshot/cli: Keep the dict keys uniform

2016-03-22T07:52:32+00:00

    Backport of http://review.gluster.org/#/c/13677/

snapshot info was using a different dictionary key
as compared to other snapshot commands. This was
throwing a recurring error log in cli.log

Change-Id: I9eb9a4541c10a45ec7673a23c89c85a7dce9f3ec
BUG: 1317363
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/13677
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Rajesh Joseph 
(cherry picked from commit 1af963dc753d97efb3cbe3e5179a2148c41c9a7d)
Reviewed-on: http://review.gluster.org/13691

cli: output of rebalance to show run time in proper format

2016-03-01T04:54:20+00:00

Backport of http://review.gluster.org/#/c/10544/

Modified tests to parse the new rebalance time format.

> Change-Id: I775f13c8046dd2aeb9d4b86a737dcebb396778b4
> BUG: 1223625
> Signed-off-by: Sakshi Bansal 
> Reviewed-on: http://review.gluster.org/10544
> Smoke: Gluster Build System 
> CentOS-regression: Gluster Build System 
> NetBSD-regression: NetBSD Build System 
> Reviewed-by: N Balachandran 
> Reviewed-by: Raghavendra G 

BUG: 1311822
Change-Id: I3c8106f7a1309f154861ce1b3efa202fa6c47c57
Signed-off-by: Sakshi Bansal 
Reviewed-on: http://review.gluster.org/13514
Smoke: Gluster Build System 
Reviewed-by: Raghavendra Talur 
Tested-by: Raghavendra Talur 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Raghavendra G

cli : provide prompt for the nfs-ganesha disable cli

2016-02-22T12:46:11+00:00

Presently, when we are executing the command "gluster nfs-ganesha disable",
the disable of nfs-ganesha cluster starts working whereas, in some cases
the user may not want to disable the cluster. So we shall let him know by
giving a prompt to let him say "yes or no" for going ahead with the disable
procedures.

Change-Id: I860dad1479f7ca16bc2736b8056b609473bef65f
BUG: 1289031
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: http://review.gluster.org/13450
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY 
Reviewed-by: Niels de Vos

cli/ afr: op_ret for index heal launch

2016-02-17T09:49:28+00:00

Backport of http://review.gluster.org/#/c/13303/

Problem:
If index heal is launched when some of the bricks are down, glustershd of that
node sends a -1 op_ret to glusterd which eventually propagates it to the CLI.
Also, glusterd sometimes sends an err_str and sometimes not (depending on the
failure happening in the brick-op phase or commit-op phase). So the message that
gets displayed varies in each case:

"Launching heal operation to perform index self heal on volume testvol has been
unsuccessful"
                (OR)
"Commit failed on . Please check log file for details."

Fix:
1. Modify afr_xl_op() to return -1 even if index healing of atleast one brick
fails.
2. Ignore glusterd's error string in gf_cli_heal_volume_cbk and print a more
meaningful message.

The patch also fixes a bug in glusterfs_handle_translator_op() where if we
encounter an error in notify of one xlator, we break out of the loop instead of
sending the notify to other xlators.

Change-Id: I957f6c4b4d0a45453ffd5488e425cab5a3e0acca
BUG: 1306922
Signed-off-by: Ravishankar N 
Reviewed-on: http://review.gluster.org/13435
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Pranith Kumar Karampuri

cli/quota : quota is not enforcing when limit is set to 0

2016-02-11T06:11:06+00:00

When limit value is set to 0, quota assumes that limit is not
set and is not enforcing currently. The patch fixes this issue by
restricting the user from setting limit value = 0.

        Backport of http://review.gluster.org/#/c/13309/

> Change-Id: I316653165cd9766600f95b5f23e5b8abcc2b41e7
> BUG: 1302554
> Signed-off-by: Manikandan Selvaganesh 

Change-Id: I83623cba54873f27bd65d5d6d85b1f8e9d895f55
BUG: 1306136
Signed-off-by: Manikandan Selvaganesh 
Reviewed-on: http://review.gluster.org/13417
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Raghavendra G