glusterfs.git/xlators/cluster, branch v3.3.0qa26

cluster/distribute: fix log level of few messages

2012-03-07T18:46:51+00:00

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

cluster/distribute: send proper 'dict' in readdirp()

2012-03-07T17:24:03+00:00

if we do the STACK_WIND from readdirp_cbk(), we were not sending
the right dictionary which made our linkfile determination a
failure.

Change-Id: Ie3f26748608f1a81123fe475d8a42bf2717475c3
Signed-off-by: Amar Tumballi 
BUG: 799887
Reviewed-on: http://review.gluster.com/2869
Tested-by: Gluster Build System 
Reviewed-by: Shishir Gowda

cluster/afr: handle node failures in lookup

2012-03-06T06:55:15+00:00

When a transaction is in progress lookup depends on inode ctx
for read-child. If the lookup fails on the read-child while
another transaction is in progress, it should select the
read-child as the next success_child which is in fresh_children.

Change-Id: I33a04b102966b63a64bacf8d2e29f0d0119fdac6
BUG: 773225
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.com/2858
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

cluster/afr: Reset re-usable sh args in sh_*_done

2012-03-05T18:36:01+00:00

The bug is observed due to stale value of active_sink count
set in metadata self-heal.

Change-Id: I41996999213c323c0f4d4db575d87b2d0b4b3fec
BUG: 798874
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.com/2849
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

fops/removexattr: prevent users from removing glusterfs xattrs

2012-03-05T17:17:47+00:00

* Each xlator prevents the user from removing xlator-specific
  xattrs like trusted.gfid by handling it in respective removexattr
  functions.

* For xlators which did not define remove and fremovexattr,
  the functions have been implemented with appropriate checks.

xlator         |     fops-added
_______________|__________________________
               |
1. stripe      |     removexattr and fremovexattr
2. quota       |     removexattr and fremovexattr

Change-Id: I98e22109717978134378bc75b2eca83fefb2abba
BUG: 783525
Signed-off-by: Rajesh Amaravathi 
Reviewed-on: http://review.gluster.com/2836
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Jeff Darcy

Revert "afr: [Un]Set the 'right' lkowner for [f]{inode|entry}_lk and the 'enclosed' fop."

2012-03-03T13:01:40+00:00

This reverts commit 2e80fdbeb6abbb23ff6789c2b98c82704883af0a.

Change-Id: I417fd43e4195d63e5b8b83dd3beb712887130e1e
Reviewed-on: http://review.gluster.com/2860
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

cluster/afr: copy the parent's gfid from child loc while building parent loc

2012-03-02T15:11:33+00:00

Suppose the process is not a fuse or nfs mounted client, and some other process
such as rebalance, then after lookups inode would not be linked to the inode
table (since the inode was created for rebalance purpose only), thus keeping
inode's gfid NULL.

And afr while building the parent loc using child loc, does not copy the
pargfid present in child'd loc structure. protocol/client will search for
the gfid either in loc or in loc->inode and assert if it cannot find the
gfid in either of them.

Change-Id: I882e449fb8b79d5c69e4a942abcd844dc4d5d30c
BUG: 799262
Signed-off-by: Raghavendra Bhat 
Reviewed-on: http://review.gluster.com/2857
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Pranith Kumar Karampuri

cluster/afr: Add new option to know which process it is in

2012-03-01T17:16:30+00:00

Afr xl needs to maintain inode-table inside the xl if it is in
self-heal-daemon. The code was depending on the option
self-heal-daemon to do this. This is wrong as the option can be
reconfigured to on/off. Added a new option which can't be
reconfigured for this purpose.

Change-Id: Idc42c403c4bd9b73d1f328427ae4158ff1420b3a
BUG: 795741
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.com/2787
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

cluster/afr: Handle errors in build_parent_loc

2012-03-01T16:44:42+00:00

BUG: 787671
Change-Id: I0b01b0f9e14a26d757748413dd71909e915c7573
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.com/2826
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

afr: [Un]Set the 'right' lkowner for [f]{inode|entry}_lk and the 'enclosed' fop.

2012-03-01T16:23:49+00:00

afr 'mangles' the lkowner inorder to ensure [f]inodelk/[f]entrylk fops from the
same application contend. But other fops that are 'visible' to the application
should operate with the lkowner provided by fuse for correct functioning of
posix-locks xlator.

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