glusterfs.git/tests/include.rc, branch v3.6.0beta3

tests: regression, can't run `prove $t` in subdirs

2014-09-21T17:31:25+00:00

In various tests we already use the pattern:

  . $(dirname $0)/../include.rc

to locate various .rc files.

Use the same pattern we already use to also find the new env.rc

Change-Id: Ib7878c3f7f6491fcec401e9adbaa696ace392fae
BUG: 1142420
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: http://review.gluster.org/8753
Tested-by: Gluster Build System 
Reviewed-by: Harshavardhana 
Tested-by: Harshavardhana 
Reviewed-by: Vijay Bellur

test: cleanup should clean all left over (stale) mounts

2014-09-13T17:34:19+00:00

This is a temporary work around to fix the spurious failures seen in ec
testcases. As per the initial analysis it looks like quota
(glusterd_quota_initiate_fs_crawl) is causing a mount point in /tmp to be stale.
Once the root cause is identified this fix can be reverted as well.

Backport of http://review.gluster.org/#/c/8703/

Change-Id: I8686f144ed298124074f749e75c13028ec00be01
BUG: 1141187
Signed-off-by: Atin Mukherjee 
Reviewed-on: http://review.gluster.org/8703
Tested-by: Gluster Build System 
Reviewed-by: Justin Clift 
Reviewed-by: Xavier Hernandez 
Reviewed-by: Vijay Bellur 
Reviewed-on: http://review.gluster.org/8708

build: make GLUSTERD_WORKDIR rely on localstatedir

2014-09-03T18:01:45+00:00

Backport from master branch - http://review.gluster.org/#/c/8246/

- Break-way from '/var/lib/glusterd' hard-coded previously,
  instead rely on 'configure' value from 'localstatedir'
- Provide 's/lib/db' as default working directory for gluster
  management daemon for BSD and Darwin based installations
- loff_t is really off_t on Darwin
- fix-off the warnings generated by clang on FreeBSD/Darwin
- Now 'tests/*' use GLUSTERD_WORKDIR a common variable for all
  platforms.
- Define proper environment for running tests, define correct PATH
  and LD_LIBRARY_PATH when running tests, so that the desired version
  of glusterfs is used, regardless where it is installed.
  (Thanks to manu@netbsd.org for this additional work)

Change-Id: I06e684ac4c26d1e74c9daf76753403ad15f79276
BUG: 1130308
Signed-off-by: Harshavardhana 
Reviewed-on: http://review.gluster.org/8486
Tested-by: Gluster Build System

tests: make dd less noisy

2014-07-16T06:00:48+00:00

Also fixed one case in quota.t where error output is expected.  There
are probably other similar cases which can be fixed separately.

Change-Id: If80fad0d9fcff6f8ca91d00f4f7b2d5f3fef4256
Signed-off-by: Jeff Darcy 
Reviewed-on: http://review.gluster.org/8298
Tested-by: Gluster Build System 
Reviewed-by: Humble Devassy Chirammal 
Reviewed-by: Prashanth Pai 
Reviewed-by: Vijay Bellur

tests: Print EXPECT style error messages rather than 'not ok'

2014-07-09T18:45:09+00:00

Change-Id: Ib23426c5ede0ab71387a6a112b313aa448b872cd
BUG: 1092850
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/8263
Tested-by: Gluster Build System 
Reviewed-by: Atin Mukherjee 
Reviewed-by: Vijay Bellur

nfs: prevent assertion error with MOUNT over UDP

2014-07-07T17:28:47+00:00

The MOUNT service over UDP runs in a separate thread. This thread does
not have the correct *THIS xlator set. *THIS points to the global (base)
xlator structure, but GF_CALLOC() requires it to be the NFS-xlator so
that assertions can get validated correctly.

This is solved by passing the NFS-xlator to the pthread function, and
setting the *THIS pointer explicitly in the new thread.

It seems that on occasion (needs further investigation) MOUNT over UDP
does not unregister itself. There can also be issues when the kernel NLM
implementation has been registered at portmap/rpcbind, so adding some
unregister procedures in the cleanup of the test-cases.

Change-Id: I3be5a420fc800bbcc14198d0b6faf4cf2c7300b1
BUG: 1116503
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/8241
Reviewed-by: Santosh Pradhan 
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

tests: Provide force_umount with 5 retries

2014-06-19T06:45:38+00:00

Change-Id: I2b5784c48eedcccb17690de438addd29075926bd
BUG: 1092850
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/8104
Reviewed-by: Jeff Darcy 
Tested-by: Gluster Build System 
Reviewed-by: Atin Mukherjee 
Reviewed-by: Vijay Bellur

tests: Avoid sleep

2014-06-16T18:11:28+00:00

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

storage/posix: Janitor should guard against dir renames.

2014-06-12T08:10:45+00:00

Problem:
Directory rename while a brick is down can cause gfid handle of that directory
to be deleted until next lookup happens on that directory.

*) Self-heal does not have intelligence to detect renames at the moment. So it
has to delete the directory 'd' using special flags, because it has to perform
'rm -rf' of that directory as it is not empty. Posix xlator implements this by
renaming the directory deleted to 'landfill' directory in '.glusterfs' where
janitor thread will perform actual rm -rf by traversing the directory. Janitor
thread wakes up every 10 minutes to check if there are any directories to be
deleted and deletes them. As part of deleting it also deletes the gfid-handles.

Steps to hit the problem:
1) On a replicate volume create a directory 'd', file in 'd' called 'f' so the
   directory 'd' is not empty.

2) bring one of the bricks down (lets call it brick-a, the other one is brick-b

3) Rename d to d1

4) When brick-a comes online again, self-heal deletes directory 'd' and creates
   directory 'd1' on brick-a for performing self-heal. So on brick-a,
   gfid-handle of 'd' pointing to 'da is deleted and recreated to point to 'd1'.

5) This directory 'b' with all its directory hierarchy (for now just the file
   'f') will be under 'landfill' directory.

6) When janitor thread wakes up and deletes directory 'd' and gfid-handle of
   'd' without realizing that it is now pointing to 'd1'. Thus 'd1' loses its
   gfid-handle

Fix:
Delete gfid-handle for a directory only when the gfid-handle is stale.

Change-Id: I21265b3bd3852f0967d916aaa21108ae5c9e7373
BUG: 1101143
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/7879
Reviewed-by: Niels de Vos 
Reviewed-by: Xavier Hernandez 
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

tests: Use uniform timeouts

2014-05-20T04:00:46+00:00

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