glusterfs.git, branch v3.3.0qa28

remove code that was part of hard resolution which is not needed anymore.

2012-03-14T18:23:25+00:00

Change-Id: I9321745a40765eff048a656a7885f12847a0a318
BUG: 781318
Signed-off-by: krishna 
Reviewed-on: http://review.gluster.com/2830
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Vijay Bellur

glusterd/mountbroker: enhance mountbroker-geo-replication.* option to take multiple volumes

2012-03-14T17:59:01+00:00

Comma can be used in the value of a "mountbroker-geo-replication.*" option
with semantics as of these examples:

  option mountbroker-geo-replication.foolabel vol1,vol2,vol3:geouser

and

  option mountbroker-geo-replication.geouser vol1,vol2,vol3

will allow geouser to mount any of the volumes vol{1,2,3} with params of a
geo-rep aux mount under label foolabel, resp. geouser

Also fix memleak in parsing of this option.

Change-Id: I5311388812f503a078a52a14f2679f5ddb33b248
BUG: 765214
Signed-off-by: Csaba Henk 
Reviewed-on: http://review.gluster.com/2818
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Venky Shankar

afr: Corrected getxattr 'key' matching in case of clrlk cmd

2012-03-14T17:58:35+00:00

- Added local->dict cleanup into afr_local_cleanup

Change-Id: Ie1b96615735a9d2a2be1757cd016dbe225aae31c
BUG: 800412
Signed-off-by: Krishnan Parthasarathi 
Reviewed-on: http://review.gluster.com/2922
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd: Fix brick op to prevent glusterd crashing

2012-03-14T16:51:13+00:00

Was building payload only for node types GD_NODE_BRICK & GD_NODE_NFS.
Payload wasn't being built for nodes GD_NODE_SHD & GD_NODE_REBALANCE, which made
glusterd crash when those operations were performed.

Also fix a compile warning.

Change-Id: Id33e21c84901d4d112c54514b7f16add31aeb950
BUG: 803313
Signed-off-by: Kaushal M 
Reviewed-on: http://review.gluster.com/2946
Tested-by: Gluster Build System 
Reviewed-by: Shishir Gowda

rpc: log in DEBUG when nfs clients try to see if ACL requests are accepted by nfs server

2012-03-14T13:01:22+00:00

Change-Id: I897b48a02ce2150d268a1a8b45163e9e1aee6cff
BUG: 801338
Signed-off-by: krishna 
Reviewed-on: http://review.gluster.com/2901
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

rpm spec file: update the 'logrotate' config file during rpm install

2012-03-14T12:59:02+00:00

so there is no need for admin to worry about logrotate configs.

Change-Id: Iec6def870d0c3550f2642ade023c03de52d6d530
Signed-off-by: Amar Tumballi 
BUG: 801372
Reviewed-on: http://review.gluster.com/2935
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

nfs: do not call inode_path on the newly created inode

2012-03-14T12:57:18+00:00

While resolving, for building the path into the loc, inode_find
is called with gfid as argument to get the inode from the inode
table. If the inode is not found, then a new inode is created.
Then the path is build using inode_path. But if the inode is
not linked to inode table (newly created inode), then gfid will
be null and inode_path returns null gfid as the path. Suppose the
lookup operation on that gfid fails, then we print the null gfid
in the log message.

To avoid it, build the path using the gfid only if inode_path
fails.

Change-Id: I2506fa8675761ddb0bc02980cd3583d9d068fc85
BUG: 802424
Signed-off-by: Raghavendra Bhat 
Reviewed-on: http://review.gluster.com/2930
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Vijay Bellur

locks: Fixed incorrect list ptr manipulation in clearing entrylks

2012-03-14T12:56:11+00:00

Avoided unwinding blocked entry lock frames inside pl_inode->mutex.

Change-Id: I424c4a1762c889c1a567c588d4ca383a6c338886
BUG: 800412
Signed-off-by: Krishnan Parthasarathi 
Reviewed-on: http://review.gluster.com/2878
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

performance/io-cache: cleanup the xlator private data completely in fini.

2012-03-14T10:59:35+00:00

Change-Id: Ib8859c57e89248ccaad94662f88944e79ec28d5a
BUG: 767862
Signed-off-by: Raghavendra G 
Reviewed-on: http://review.gluster.com/791
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Vijay Bellur

fuse-bridge/graph-cleanup: don't provide a cbk for cleanup syncop task

2012-03-14T10:57:32+00:00

without a cbk, syntask_new returns only after the task is complete.
Hence we don't have to wait on a conditional variable in the caller.

Change-Id: Ie83894aa6fc02cc3a973930e67ae2b35de3b7647
BUG: 767862
Signed-off-by: Raghavendra G 
Reviewed-on: http://review.gluster.com/2870
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Vijay Bellur