glusterfs-quota.git/tests, branch test

tests: Avoid timing delays caused by fsync

2013-07-23T10:37:54+00:00

Change-Id: I2da53dd14d7352bdc878fce5a9019a955e150ce9
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/5377
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

cluster/afr: Handle parallel hardlinks self-heal

2013-07-23T07:33:39+00:00

Change-Id: Ieda11870c65edae500140b6c061f15a7b3f264f3
BUG: 986905
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/5370
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

move 'xlators/marker/utils/' to 'geo-replication/' directory

2013-07-22T08:53:03+00:00

Change-Id: Ibd0faefecc15b6713eda28bc96794ae58aff45aa
BUG: 847839
Original Author: Amar Tumballi 
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/5133
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

mount/fuse: unlink the inode on revalidate if entry not found

2013-07-19T04:16:06+00:00

If an inode/dentry is linked via a client and removed via a
separate client, the inode/dentry mapping in the initial client
remains. A lookup of the removed name on the initial client
typically returns ENOENT once the associated caches expire. If the
initial client has multiple dentries linked to the same inode,
however, lookups on the non-removed dentry create windows of time
where lookups on the stale/removed name return successfully. This
occurs because the stale mapping resolves to the still valid inode
and tricks md-cache into returning valid lookup data.

To correct this situation, unlink the stale inode mapping on a
failed (ENOENT) revalidation lookup (i.e., when fuse has resolved
the inode but a lookup returns ENOENT). Note that with this change,
the state still occurs until an md-cache window has expired,
allowed a lookup to pass through to the server and given the fuse
translator an opportunity to clean up.

Change-Id: I47dde2f11e2ef5b8dd51e9ac8be0f36cdb5081a3
BUG: 985074
Signed-off-by: Brian Foster 
Reviewed-on: http://review.gluster.org/5337
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

tests: call 'cleanup' at the end of each test

2013-07-15T17:44:27+00:00

Some tests do not cleanup after themselves. That is bad behaviour and
makes it difficult to run single tests and verify the state of the
system afterwards.

Change-Id: I4ac5401d790d6bc81e6975fd1384874b21d6cf8a
BUG: 983975
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/5328
Tested-by: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY 
Reviewed-by: Anand Avati

afr: customize client-pid=-1 xtime aggregation to tolerate a replica down

2013-07-15T08:24:19+00:00

Using the new 'pluggable policies' API of libxlator.

Change-Id: Ie7528182dff8fb42c6e8287a106d3057944df775
BUG: 847839
Original Author: Csaba Henk 
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/4904
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

mount/fuse: Provide option to use/not use kernel-readdirp

2013-07-12T14:36:05+00:00

By default fuse kernel readdirp usage in fuse xlator is off.
When mount option use-readdirp=yes is provided it starts using
fuse-kernel's readdirp.

Change-Id: Id37edc53b1adc1638186d956c2f74c1e4e48aa59
BUG: 983477
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/5322
Tested-by: Gluster Build System 
Reviewed-by: Raghavendra Bhat 
Reviewed-by: Vijay Bellur

cli: check for null in is_server_debug_xlator()

2013-07-12T11:14:12+00:00

Command: gluster volume set  diagnostics.client-log-level trace
Expected output:
"volume set: failed: option log-level trace: 'trace' is not valid
(possible options are DEBUG, WARNING, ERROR, INFO, CRITICAL, NONE,
TRACE.)"
Current output: gluster cli receives a segmentation fault
Fix: check for NULL before calling strstr

Change-Id: If4c7a85a635849a388cf122543e12349c109643c
BUG: 982174
Signed-off-by: Ravishankar N 
Reviewed-on: http://review.gluster.org/5298
Reviewed-by: Kaushal M 
Tested-by: Gluster Build System

tests: Don't use stripe-replicate volume in bug-905864.t

2013-07-11T05:54:42+00:00

Today, stripe doesn't follow a deterministic order in sending posix
locks to its subvolume. This may lead to dead locks. To avoid
intermittent test failures, we modify bug-905864.t to run on replicate
volume.

Change-Id: I38b72f30bc31576d3ca642f0029cc8749314b1dd
BUG: 905864
Signed-off-by: Krishnan Parthasarathi 
Reviewed-on: http://review.gluster.org/5072
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

nfs: AUTH support for exported sub-directories

2013-07-10T05:55:12+00:00

Problem: NFS allows exporting subdirectories but there is not support for
providing AUTH on per directory basis.

Fix: Modified nfs.export-dir to include AUTH parameters
 e.g. nfs.export-dir "/dir1(10.1.1.2),/dir2(10.1.1.0/24|host1)

During mount operation NFS will check if the IP from where the connection is made
is configured in the AUTH parameter, else the mount operation will fail with
EACCES error.

Updated admin-guide and volume set help message.

Change-Id: I5c6d22edb168b4f46376d1cd6878cd065fc081cc
BUG: 968227
Signed-off-by: Rajesh Joseph 
Reviewed-on: http://review.gluster.org/5124
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur