glusterfs.git/xlators/nfs/server, branch v3.3.0qa33

nlm: print the reason of failure when clnt_create fails to create the client object

2012-04-02T09:42:03+00:00

Change-Id: Icc271e2166dbccc2cc12029e26c674fdb79fe975
BUG: 808390
Signed-off-by: Raghavendra Bhat 
Reviewed-on: http://review.gluster.com/3061
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd: Include port in nfs status

2012-04-02T09:41:18+00:00

Change-Id: I679e491e801b694e8a0f93dd87cf540441dae927
BUG: 806877
Signed-off-by: Kaushal M 
Reviewed-on: http://review.gluster.com/3060
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

nlm: do not destroy the NULL client object

2012-03-30T22:50:42+00:00

Change-Id: Ie1946b33353a91a266d2b21727d0c8eaa06af7f9
BUG: 808341
Signed-off-by: Raghavendra Bhat 
Reviewed-on: http://review.gluster.com/3046
Tested-by: Gluster Build System 
Reviewed-by: Jeff Darcy 
Reviewed-by: Anand Avati

core: fix all the iobuf related refs and unrefs

2012-03-29T14:54:34+00:00

reviewed the code against all the possible places where
iobuf/iobref ref unref are present, and hopefully fixed most of
the issues around memory leaks with respect to iobuf

Change-Id: I9aa30326962991f8e23acedd389a0e962e097885
Signed-off-by: Amar Tumballi 
BUG: 797875
Reviewed-on: http://review.gluster.com/2994
Tested-by: Gluster Build System 
Reviewed-by: Jeff Darcy 
Reviewed-by: Vijay Bellur

core: adding extra data for fops

2012-03-22T23:40:27+00:00

with this change, the xlator APIs will have a dictionary as extra
argument, which is passed between all the layers. This can be
utilized for overloading in some of the operations.

Change-Id: I58a8186b3ef647650280e63f3e5e9b9de7827b40
Signed-off-by: Amar Tumballi 
BUG: 782265
Reviewed-on: http://review.gluster.com/2960
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

rpc-clnt: separate out connection_cleanup() from destroy()

2012-03-19T16:14:40+00:00

noticed that there are possibilities where one would like to do a
connection_cleanup() before destroying a RPC connection itself, also
current code is such that, rpc_clnt_connection_cleanup() does
rpc_clnt_ref() and unref(), creating a race window/double unref
possibilities in the code.

by separating out the functions, this race window/double fault can be
prevented.

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

mgmt/glusterd : volume set validation fixes

2012-03-18T07:52:40+00:00

This is the new version of the patch by Kaushik at review.gluster.com/699

The following new option types have been introduced:
 * GF_OPTION_TYPE_INTERNET_ADDRESS_LIST
 * GF_OPTION_TYPE_PRIORITY_LIST
 * GF_OPTION_TYPE_SIZE_LIST
and option types of several options in translators have been updated to use the
new types.

valid_internet_address(), valid_ipv4_address() & valid_ipv6_address() functions
has been updated for * wildcard matching. Previously used standalone wildcard
address checking functions have been removed.

Changes have been done to stripe translator to correctly set, update and use
stripe-blocksize. Also minimum value for block-size has been set to 16KB.

Change-Id: I2aa484ff695f6a915a8fc9a9f965cf0344f41d59
BUG: 765248
Signed-off-by: Kaushal M 
Reviewed-on: http://review.gluster.com/2899
Tested-by: Gluster Build System 
Reviewed-by: Shishir Gowda 
Reviewed-by: Anand Avati

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

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

nfs: no need to recalculate the 'ino' from gfid

2012-03-14T10:05:54+00:00

it is guaranteed to be sent properly from posix layer itself now

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