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

quota/disperse: handle inode quotas in xattr aggregate

2015-04-14T05:01:18+00:00

with the inode quota feature, quota size is now
increased from 64bit to 192bits which contains
values of 'file size', 'file count' and 'dir count'

This change in quota size xattr needs to be handled
in disperse xattr aggregation

Signed-off-by: vmallika 

Change-Id: I5fd28aa9f5b8b6cba83a98360236417a97ac16ee
BUG: 1207967
Reviewed-on: http://review.gluster.org/10112
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Gluster Build System 
Reviewed-by: Sachin Pandit 
Reviewed-by: Raghavendra G 
Tested-by: Raghavendra G

quota/cli: validate quota hard-limit option

2015-04-10T11:21:48+00:00

Quota hard-limit is supported only upto: 9223372036854775807 (int 64)

In CLI, it is allowed to set the value upto 16384PB (unsigned int 64),
this is not a valid value as the xattrop for quota accounting and
the quota enforcer operates on a signed int64 limit value.

This patches fixes the problem in CLI and allows user to set
the hard-limit value only from range 0 - 9223372036854775807

Change-Id: Ifce6e509e1832ef21d3278bacfa5bd71040c8cba
BUG: 1206432
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/10022
Tested-by: Gluster Build System 
Reviewed-by: Kaushal M 
Reviewed-by: Vijay Bellur

gluster-cli : Removing logically dead code

2015-04-10T10:02:23+00:00

Coverity CID: 1124451

Change-Id: I7b2901fdd2ace4666f9e2c6deaf3838322a1c6ff
BUG: 789278
Signed-off-by: Nandaja Varma 
Reviewed-on: http://review.gluster.org/9579
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd/snapshot: Fix CLI msg for snap limit set

2015-04-10T08:04:33+00:00

Change of message from "will lead to deletion of snaps"
to "Will limit creation of new snaps" when setting the
snapshot limits.

Change-Id: I4732555bb35d3ad30c2cef6ea6c7da42a8edf35d
BUG: 1116263
Signed-off-by: Joseph Fernandes 
Reviewed-on: http://review.gluster.org/8236
Tested-by: Gluster Build System 
Reviewed-by: Avra Sengupta 
Reviewed-by: Krishnan Parthasarathi 
Tested-by: Krishnan Parthasarathi

gluster-cli : Extra checks for word_count removed.

2015-04-10T06:40:26+00:00

Coverity IDs:
1124453
1124454

In the first case, In the beginning of the function check is made
to see of the word_count is less than 4. If yes it returns. So it
wouldn't reach this part if that check takes the true path. So
this code is logically dead.

In second and third case, this is in false branch for word_cound <6.
So word_count can't possibly be less than 5 at this point.

Change-Id: Id5e1c81045ce7bc0ee6b7612ea54ef2b7f54b699
BUG: 789278
Signed-off-by: Nandaja Varma 
Reviewed-on: http://review.gluster.org/9582
Tested-by: Gluster Build System 
Reviewed-by: Humble Devassy Chirammal 
Reviewed-by: Vijay Bellur

glusterd: remove-brick status/stop should not show output for non-existing brick

2015-04-09T17:21:06+00:00

Previously when user start remove-brick operation on a volume then by
giving non-existing brick for remove-brick status/stop command it was
showing remove-brick status/stoping remove-brick operation on a volume.

With this fix it will validate bricks which user have given for
remove-brick status/stop command and if bricks are part of volume then
it will show statistics of remove-brick operation otherwise it will show
error "Incorrect brick  for ".

Change-Id: I151284ef78c25f52d1b39cdbd71ebfb9eb4b8471
BUG: 1121584
Signed-off-by: Gaurav Kumar Garg 
Reviewed-on: http://review.gluster.org/9681
Tested-by: Gluster Build System 
Reviewed-by: Krishnan Parthasarathi 
Tested-by: Krishnan Parthasarathi

cli: Allow options prefixed with '--' for geo-rep config cmds

2015-04-09T11:36:04+00:00

Geo-replications allows users to send rsync_options from
cli but while parsing, options prefixed with '--' are
treated as unrecognized apart from a few options. Because
of this rsync_options can't be set through cli. This
patch allows such options if it's a geo-rep config command.

e.g.
gluster vol geo-rep master fedora1::slave config rsync-options \
"--bwlimit=1.5m"

Change-Id: I4b4f10c0efd3f3a362ece65e697d5ce1498f84ac
BUG: 1168108
Signed-off-by: Kotresh HR 
Reviewed-on: http://review.gluster.org/9198
Reviewed-by: Aravinda VK 
Tested-by: Gluster Build System 
Reviewed-by: Krishnan Parthasarathi 
Tested-by: Krishnan Parthasarathi

cli: Fixing dereference after null check

2015-04-09T09:46:35+00:00

     and dead code removal

CID: 1124609
CID: 1124596
CID: 1124471
CID: 1124475
CID: 1124476
The pointer variables are checked before
dereferencing and the dead code is removed

BUG: 789278
Change-Id: Ia532733a64401d71ccf1f2b6e434d7bc910e0ed1
Signed-off-by: arao 
Reviewed-on: http://review.gluster.org/10083
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

cli: gluster volume help should give sufficient information for bitrot

2015-04-09T04:39:20+00:00

Previously command "gluster volume help | grep bitrot" was not giving
sufficient information for bitrot.

With this fix command "gluster volume help" will give appropriate information
for bitrot.

Change-Id: Ic385c760d4ecbfb16ff5d90dba8940b3616035e5
BUG: 1207532
Signed-off-by: Gaurav Kumar Garg 
Reviewed-on: http://review.gluster.org/10133
Tested-by: Gluster Build System 
Reviewed-by: Kaushal M

glusterd: Support distributed replicated volumes on hot tier

2015-04-08T07:28:21+00:00

We did not set up the graph properly for hot tiers with replicated
subvolumes. Also add check that the file has not already been moved
by another replicated brick on the same node.

Change-Id: I9adef565ab60f6774810962d912168b77a6032fa
BUG: 1206517
Signed-off-by: Dan Lambright 
Reviewed-on: http://review.gluster.org/10054
Reviewed-by: Joseph Fernandes 
Tested-by: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY