glusterfs.git/tests/basic, branch v3.6.2beta2

afr : glfs-heal implementation

2015-01-06T10:04:49+00:00

    Backport of http://review.gluster.org/6529
and http://review.gluster.org/9119

Change-Id: Ie420efcb399b5119c61f448b421979c228b27b15
BUG: 1173528
Signed-off-by: Anuradha 
Reviewed-on: http://review.gluster.org/9335
Reviewed-by: Ravishankar N 
Tested-by: Gluster Build System 
Reviewed-by: Raghavendra Bhat

mgmt/glusterd: Validate the options of uss

2014-12-24T11:36:38+00:00

Change-Id: Id13dc4cd3f5246446a9dfeabc9caa52f91477524
BUG: 1175755
Signed-off-by: Varun Shastry 
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/8133
Tested-by: Gluster Build System 
Reviewed-by: Krishnan Parthasarathi 
Tested-by: Krishnan Parthasarathi 
Signed-off-by: Sachin Pandit 
Reviewed-on: http://review.gluster.org/9304
Reviewed-by: Raghavendra Bhat

uss/gluster: creating file/directories inside .snaps should fail with EROFS.

2014-12-22T12:19:04+00:00

When an attempt is made to create file/directories inside .snaps, it
fails with wrong error message as "Stale file handle". It should fail
with "Read-only file system"

Change-Id: I3a812a0afc4762cbb71ab180b9394c866e576a66
BUG: 1175730
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/9039
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur 
Signed-off-by: Sachin Pandit 
Reviewed-on: http://review.gluster.org/9300
Reviewed-by: Raghavendra Bhat

glusterd/snapshot: Snapshot should be deactivated when it is created.

2014-12-19T06:52:22+00:00

By default snapshot should be deactivated and this should be a
configurable option.

This behaviour can be configured by the command below:
gluster snapshot config activate-on-create 

Change-Id: I1911595c32beed43bb2fca4bf99f0d264b422513
BUG: 1170921
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/8985
Tested-by: Gluster Build System 
Reviewed-by: Avra Sengupta 
Reviewed-by: Rajesh Joseph 
Reviewed-by: Kaushal M 
Signed-off-by: Sachin Pandit 
Reviewed-on: http://review.gluster.org/9241
Reviewed-by: Raghavendra Bhat

tests: spurious failures fix for quota-anon-fd-nfs.t

2014-12-10T18:10:11+00:00

Change-Id: I4f7ee68c514d8d322e25cf74167f288a8b6f8164
BUG: 1165938
Signed-off-by: Atin Mukherjee 
Reviewed-on: http://review.gluster.org/9108
Tested-by: Gluster Build System 
Reviewed-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/9148
Reviewed-by: Raghavendra Bhat 
Tested-by: Raghavendra Bhat

tests: regression test portability - quota-anon-fd-nfs.t

2014-12-10T06:19:38+00:00

Fix portability problems in quota-anon-fd-nfs.t
- Use mount_nfs wrapper and include nfs.rc to get it defined.
- umount NFS before cleanup to avvoid deadlocks.
- umount -l is Linux-specific, use umount -f on BSD.
- wait for 1s for portmap registration before mouting NFS.
- mount from $H0 instead of localhost: the later fails on NetBSD.
- Test quota without filling GB of data, 20MB is enough and it
  will be gentle with smaller setups.
- wait for write behind to complete before testing quota overflow

BUG: 1165938
Change-Id: I097d5faed2fa7b6438aaa56def85172f23bbe7dc
Signed-off-by: Emmanuel Dreyfus 
Reviewed-on: http://review.gluster.org/8969
Reviewed-by: Shyamsundar Ranganathan 
Reviewed-by: Niels de Vos 
Tested-by: Kiran Patil 
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur 
Reviewed-on: http://review.gluster.org/8997
Reviewed-by: Raghavendra Bhat 
Tested-by: Raghavendra Bhat

protocol/server: No root-squash checks for self-heal pid

2014-12-10T06:17:58+00:00

         Backport of http://review.gluster.org/9231

Problem:
Self-heal pid used to be -1 which was colliding with gsyncd. Gsyncd
was not checked for root-squash authentication. Recently self-heal
pid changed to -6, but root-squash authentication is not disabled
for this.

Fix:
disable root-squash authentication for self-heal

Change-Id: I594a732d800902ce805f849813631da36d8d3dc7
BUG: 1170514
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/9234
Tested-by: Gluster Build System 
Reviewed-by: Raghavendra Bhat 
Tested-by: Raghavendra Bhat

tests: spurious failure fix in mgmt_v3_locks.t

2014-11-30T07:29:26+00:00

Change-Id: I7c4599648b5d47d93a447e58c063fab21e8f9ef7
BUG: 1165938
Signed-off-by: Atin Mukherjee 
Reviewed-on: http://review.gluster.org/9114
Tested-by: Gluster Build System 
Reviewed-by: Kaushal M 
Tested-by: Kaushal M 
Reviewed-on: http://review.gluster.org/9149
Reviewed-by: Raghavendra Bhat

ec: Correctly handle quota xattrs

2014-11-15T18:01:14+00:00

This is a backport of http://review.gluster.org/8990/

Change-Id: I35e11d83c318210d44b918e847cf13db35b01510
BUG: 1158088
Signed-off-by: Xavier Hernandez 
Reviewed-on: http://review.gluster.org/8992
Tested-by: Gluster Build System 
Reviewed-by: Dan Lambright

features/snapview-server: check if the reference to the snapshot world is correct before doing any fop

2014-10-30T18:39:15+00:00

The following operations might lead to problems:
* Create a file on the glusterfs mount point
* Create a snapshot (say "snap1")
* Access the contents of the snapshot
* Delete the file from the mount point
* Delete the snapshot "snap1"
* Create a new snapshot "snap1"

Now accessing the new snapshot "snap1" gives problems. Because the inode and
dentry created for snap1 would not be deleted upon the deletion of the snapshot
(as deletion of snapshot is a gluster cli operation, not a fop). So next time
upon creation of a new snap with same name, the previous inode and dentry itself
will be used. But the inode context contains old information about the glfs_t
instance and the handle in the gfapi world. Directly accessing them without
proper check leads to ENOTCONN errors. Thus the glfs_t instance should be
checked before accessing. If its wrong, then right instance should be obtained
by doing the lookup.

Change-Id: I975245b8f6b7fea0a90eb5e36e8149d12457ac10
BUG: 1158791
Reviewed-on: http://review.gluster.org/9007
Reviewed-by: Vijay Bellur 
Tested-by: Vijay Bellur