glusterfs.git, branch v3.4.1qa3

cluster/dht: Treat migration failures due to space constraints as skipped

2013-09-20T06:39:40+00:00

Currently rebalance/remove-brick op's display migration failed count even
for files which failed due to space issues (not enough space for file, or
migration leading to cluster imbalance)

These will now be counted as skipped, and rebalance/remove-brick status
will display the additional counter

BUG: 989846
Change-Id: I4efa7ce69dd43680ff47181afed0c561954c5080
Signed-off-by: shishir gowda 
Reviewed-on: http://review.gluster.org/5977
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

gfapi: implement a minimial glfs_fini()

2013-09-19T21:28:50+00:00

At the very least, we should PARENT_DOWN on the currently active
graph and disconnect ourselves from glusterd.

Further cleanups underway.

Change-Id: I9276686a84b0975b5ce272b4cbec1b80920d5c5c
BUG: 1004519
Signed-off-by: Anand Avati 
Reviewed-on: http://review.gluster.org/5903
Tested-by: Gluster Build System

cli,glusterd: Task parameters in xml output

2013-09-19T21:08:02+00:00

 Backport of 91cd0eae2cc1d96cbafa6457835f146503355238 from master

This patch introduces task parameters for the asynchronus task shown in
volume status. The parameters are only given for xml output. The
parameters shown currently are,
- source and destination bricks for replace-brick tasks
  ......
        
          
            Replace brick
            3d1a1005-9d2e-4ae0-bd62-577bc1d333a3
            1
            
              archm:/export/test4
              archm:/export/test-replace1
            
          
        
  ......
- list of bricks being removed for remove-brick tasks
  ......
        
          
            Remove brick
            901c20ca-0da2-41de-8669-5f0caca6b846
            1
            
              archm:/export/test2
              archm:/export/test3
            
          
        
  ......

The changes for non-xml output will be done in a subsequent patch.

BUG: 916577
Change-Id: Iade8a4974aefc5ffb080553496ae5a3169055090
Signed-off-by: Kaushal M 
Reviewed-on: http://review.gluster.org/5973
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

cli: add aggregate status for rebalance and remove-brick status xml output

2013-09-19T21:07:45+00:00

 Backport of 91e4b7aa1361087317238b9bf6427ef274737c8c from master

Add aggregate status information in  section of gluster volume
'rebalance status' and 'remove-brick status cli xml output.

The aggregate status determined based on the most critical level
and the aggregate status will have 'Complete' only when all
individual status are 'Complete'.

BUG: 1006813
Change-Id: I803d4bfb31dbda53b5665332263576c910562805
Original-author: Timothy Asir 
Signed-off-by: Kaushal M 
Reviewed-on: http://review.gluster.org/5972
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

glusterd: Don't reset rebalance status on add-brick

2013-09-19T21:07:06+00:00

 Backport of 67c28b19355c47e96d1420405cc38753a3e5f9be from master

The rebalance status was being reset to 'Not started' when add-brick was
performed. This would lead to odd cases where a 'rebalance status' on a
volume would show status as 'not started' but would also include the
rebalance statistics. This also affected the showing of asynchronus task
status in 'volume status' command.

By not resetting the status prevent the above issues from happening.
Since we use the running/not-running of the rebalance process as the
check when performing other operations we can safely leave the rebalance
stats collected on an add-brick.

BUG: 1006247
Change-Id: Idade88d9e5a6f27659490b3e6d85495d426ef0a3
Signed-off-by: Kaushal M 
Reviewed-on: http://review.gluster.org/5971
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

rpcsvc: allocate large auxgid list on demand

2013-09-19T21:06:33+00:00

For rpc requests having large aux group list, allocate large list
on demand. Else use small static array by default.

Without this patch, glusterfsd allocates 140+MB of resident memory
just to get started and initialized.

Change-Id: I3a07212b0076079cff67cdde18926e8f3b196258
Signed-off-by: Anand Avati 
BUG: 953694
Reviewed-on: http://review.gluster.org/5927
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-on: http://review.gluster.org/5928

mount/fuse: Implement forget in cbks for fuse.

2013-09-19T21:05:30+00:00

With the introduction of inode_ctx_set in fuse as part of  2991503d014,
forget cbk gets called for fuse xlator. Though nothing needs to be done
inf forget_cbk, excessive log messages of the following kind are observed:

[2013-09-16 06:09:50.758063] W [defaults.c:1331:default_forget]
(-->/usr/local/lib/glusterfs/3git/xlator/mount/fuse.so(+0xa1f2) [0x7f51432781f2]
(-->/usr/local/lib/libglusterfs.so.0(inode_unref+0x3c) [0x7f5144e5
816c] (-->/usr/local/lib/libglusterfs.so.0(+0x2d061) [0x7f5144e58061]))) 0-fuse:
xlator does not implement forget_cbk

This patch prevents such log messages from being seen.
Signed-off-by: Vijay Bellur 
BUG: 979910
Change-Id: Ie5874138f46822b10ff4213bd1134d78330ec460
Reviewed-on: http://review.gluster.org/5932
Reviewed-by: Anand Avati 
Tested-by: Anand Avati 
Reviewed-on: http://review.gluster.org/5975
Tested-by: Gluster Build System

cli: Fix 'status all' xml output when volumes are not started

2013-09-19T17:29:42+00:00

 Backport of 7d9bc0d21408c31651a65a6ec0e67c3b8acd0fde from master

CLI now only outputs one XML document for 'status all' only containing
those volumes which are started.

BUG: 1004218
Change-Id: I119ac40282380886b46a09fd9a19d35115fd869d
Signed-off-by: Kaushal M 
Reviewed-on: http://review.gluster.org/5970
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

cli: Add statusStr xml tag to task list and rebalance/remove brick status

2013-09-19T17:28:27+00:00

 Backport of cd7951aa31ae4bbdf35fc6d1f2466636844b889d from master

New xml tag statusStr added to following gluster cli commands
gluster volume status all --xml (For Task status)
gluster volume rebalance  status --xml
gluster volume remove-brick   status --xml

Example(volume status all):

    Rebalance
    82d8d122-8738-4144-8507-d93fc98b61df
    3
    completed


Example(volume rebalance  status)

    localhost
    0
    0
    0
    0
    3
    completed


Also modified task status as string instead of showing number
in gluster volume status all

Example:
Status of volume: gv1
Gluster process                                         Port    Online  Pid
------------------------------------------------------------------------------
Brick sumne.sumne:/gfs/b1                               49154   Y       15489
Brick sumne.sumne:/gfs/b2                               49155   Y       15493
NFS Server on localhost                                 N/A     N       15913

           Task                                      ID         Status
           ----                                      --         ------
      Rebalance    82d8d122-8738-4144-8507-d93fc98b61df      completed

BUG: 1003521
Change-Id: I2f6845b621cbd5a74aeb3a3195f944536745e0ec
Original-author: Aravinda VK 
Signed-off-by: Kaushal M 
Reviewed-on: http://review.gluster.org/5969
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

tests: Remove grep process entries from pidgrep

2013-09-15T23:16:27+00:00

Problem:
We were picking process with lowest pid from ps|grep
result. However, lowest pid need not be oldest process
as recycling of PIDs can take place.

Solution:
Removed grep process entries from ps entries using
grep -v grep.

Change-Id: I2b9687a05a34cf6358f773183770d69a3fb9eb10
BUG: 858488
Signed-off-by: Raghavendra Talur 
Reviewed-on: http://review.gluster.org/5930
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati