glusterfs.git/tests/include.rc, branch v3.7.19

tests: Backport all changes to tests dir

2016-05-04T18:47:11+00:00

Test framework should be the same on all the branches. This is a copy
of all the files under tests dir from master branch. New tests in
master have not been backported, but changes to existing tests have
been.

Change-Id: I75747c525aabbd9247473dd29b3a0e7a7d93c827
BUG: 1316533
Signed-off-by: Raghavendra Talur 
Reviewed-on: http://review.gluster.org/13683
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System

extras: Add namespace for options in group-virt.example

2016-04-13T13:00:26+00:00

Commit 23ccabbeb7 introduced a new key "disperse.eager-lock" which
causes a conflict with key "cluster.eager-lock" when option is used
without the qualifying namespace. group-virt.example which gets
installed as /var/lib/glusterd/ groups/virt contains options without
namespace qualifiers. This patch adds the appropriate namespace to all
options in group-virt.example.

Change-Id: I2c09dd10d44138410d889ddeb805f01c641c6780
BUG: 1325630
Signed-off-by: Vijay Bellur 
Reviewed-on: http://review.gluster.org/13929
Reviewed-by: Pranith Kumar Karampuri 
Reviewed-on: http://review.gluster.org/13958
Smoke: Gluster Build System 
Tested-by: Kaushal M 
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Kaushal M

uss/gluster: generate gfid for snapshot files from snapname and gfid

2016-03-23T11:03:52+00:00

This is a backport of http://review.gluster.org/#/c/9255/

If 'a' and 'b' are hardlinks, we need to generate a virtual
gfid for these files so that the inode number for 'a' and 'b'
are same.

Generate gfid as below:
gfid_of_a = MD5(snapname + back_end_gfid(a))
if '/dir1/a' and '/dir2/b' are hardlinks, then inode number should be
same for
all below files:
/mnt/.snaps/snap1/dir1/a
/mnt/.snaps/snap1/dir2/b
/mnt/dir1/.snaps/snap1/a
/mnt/dir2/.snaps/snap1/b

> Change-Id: Ifda793455610e554f3f1e4cbb90d44c02cda4b0f
> BUG: 1171703
> Signed-off-by: vmallika 

Change-Id: I917b2fe2915d88f69700bc8c3283e9c613e13bb8
BUG: 1316099
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/13656
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Rajesh Joseph

storage/posix: Implement .unlink directory

2016-01-25T11:37:10+00:00

Problem: For EC volume, If a file descriptor is open and
file has been unlinked, any further write on that fd will
fail. When a write request comes, EC internally reads some
blocks using anonymous fd. This read will fail as the file
has already been unlinked.

Solution: To solve this issue, we are using .unlink directory
to keep track of unlinked file. If a file is to be unlinked
while its fd is open, move this to .unlink directory and unlink
it from .glusterfs and real path. Once all the fd will be closed,
remove this entry form .unlink directory.

master -
http://review.gluster.org/#/c/12816/

Change-Id: I8344edb0d340bdb883dc46458c16edbc336916b9
BUG: 1291557
Signed-off-by: Ashish Pandey 
Reviewed-on: http://review.gluster.org/12968
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Pranith Kumar Karampuri 
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System

NetBSD regression reliability: properly cleanup loopback devices

2016-01-20T10:08:24+00:00

When a loopback device is configured and we forcibly unmount the
filesystem containing the backing store, further vnconfig -l will
complain "vnconfig: VNDIOCGET: Bad file descriptor" causing
failures.

We fix this by iterating on all loopback devices available in /dev,
testing for this condition and manually unconfiguring when it
happens.

Backport of: I17b956a8ed28a7767f2d0dda83b93c523d3238c2

BUG: 1212676
Change-Id: I9d6fdd859572b653e1144c7d9d98a977cc3e255a
Signed-off-by: Emmanuel Dreyfus 
Reviewed-on: http://review.gluster.org/13205
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Pranith Kumar Karampuri 
CentOS-regression: Gluster Build System

tests: New simple geo-rep regression test suite

2015-11-27T09:32:08+00:00

This is a new simple regression test suite for
geo-replication. This is written keeping in mind
the run time for regression test. The existing
regression test suite is rigorous one and could
be run nightly. Hence the existing geo-rep tests
are being removed as part of this.

Also re-enable geo-rep regression with this patch.

Thanks Aravinda for initial template and plan.

BUG: 1284746
Change-Id: I9eea88c267d9e838022b7c9201e2ba4bb04f612e
Reviewed-on: http://review.gluster.org/11058
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Aravinda VK 
Signed-off-by: Kotresh HR 
Reviewed-on: http://review.gluster.org/12726
Reviewed-by: Venky Shankar

tests: Await for graph switch before testing open fop count

2015-05-28T09:34:28+00:00

In performance/open-behind.t, a test for open fop reaching the brick is done by
switching off open-behind and performing a read operation. If the read operation
is performed before a graph switch, the read happens on the old graph and hence
open does not get accounted in the brick.

To overcome this EXPECT_WITHIN 10 seconds has now been added to ensure that a
graph switch has happened. The read operation happens subsequently after the
graph switch.

Cleaned up a "No volumes present" message from stderr while doing this.

Change-Id: I05f7cbfd1ce51782f5ab778468a980d3732509a2
BUG: 1225077
Signed-off-by: Vijay Bellur 
Reviewed-on: http://review.gluster.org/10941
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System
Reviewed-by: Krishnan Parthasarathi

tests: write log for glupy.t to the standard log directory

2015-05-26T17:35:48+00:00

There is (or was) a spurious test in glupy.t for which a separate log
file was setup. The directory where the log is saved, is not available
on NetBSD and this causes glupy.t to always fail, without a log.

Instead of hard-coding the path to the log, use "gluster --print-logdir"
to provide a LOGDIR environment variable. glupy.t now writes the log to
an existing directory.

Cherry picked from commit cfca748fef28170377b868871b0dd980c1f151f6:
> BUG: 1163543
> Change-Id: Ifa73198d06fa267856d0da9d25a4380329909124
> Signed-off-by: Niels de Vos 
> Reviewed-on: http://review.gluster.org/10801
> Tested-by: NetBSD Build System
> Tested-by: Gluster Build System 
> Reviewed-by: Vijay Bellur 

Change-Id: Ifa73198d06fa267856d0da9d25a4380329909124
BUG: 1225077
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/10920
Tested-by: NetBSD Build System
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

tests: fix failures due to not unmounting $M2 (/mnt/glusterfs/2)

2015-05-06T09:34:37+00:00

Our failure to unmount meant that both mkdir and rmdir would fail in
cleanup().  Because one of those mkdirs was the last thing cleanup()
executed, it would fail, so the test would fail, so the entire
regression run would fail.  The fix has two parts.

(1) Unmount the offending directory.

(2) Make sure cleanup() returns success even if that last mkdir
    failed.

That might keep us from consistently blowing up regression runs on the
very first tests (basic/afr/data-self-heal.t) that we execute.

Change-Id: I7a9761bd28761a5ee2face3db8112e9c3f6c5dc8
BUG: 1163543
Signed-off-by: Jeff Darcy 
Reviewed-on: http://review.gluster.org/10536
Reviewed-by: Justin Clift 
Reviewed-by: Kaleb KEITHLEY 
Tested-by: Gluster Build System 
Reviewed-on: http://review.gluster.org/10557
Tested-by: Vijay Bellur

tests: Fix spurious failures

2015-05-06T06:02:17+00:00

        Backport of: http://review.gluster.org/10480
                     http://review.gluster.org/10487
                     http://review.gluster.org/10488
                     http://review.gluster.com/10540

- Use REBALANCE_TIMEOUT in EXPECT_WITHIN
- Use fdatasync to prevent write - behind from giving success
- Add logfile to glupy
- Check aux umount is unmounted for quota tests
- Disable flush behind so that file will be closed

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