glusterfs.git/tests, branch v3.4.4beta1

storage/posix: do not dereference gfid symlinks before posix_handle_mkdir_hashes()

2014-05-22T11:09:16+00:00

Whenever a new directory is created, its corresponding gfid file must
also be created. This was done first calling MAKE_HANDLE_PATH() to get
the path of the gfid file, then calling posix_handle_mkdir_hashes() to
create the parent directories of the gfid, and finally creating the
soft-link.

In normal circumstances, the gfid we want to create won't exist and
MAKE_HANDLE_PATH() will return a simple path to the new gfid. However if
the volume is damaged and a self-heal is running, it is possible that we
try to create an already existing gfid. In this case, MAKE_HANDLE_PATH()
will return a path to the directory instead of the path to the gfid.

To solve this problem, every time a path to a gfid is needed, a call to
MAKE_HANDLE_ABSPATH() is made instead of the call to MAKE_HANDLE_PATH().

BUG: 1099955
Change-Id: I5bcd2b3c38d172c75946f33519e057e76d960a24
Signed-off-by: Xavier Hernandez 
Reviewed-on: http://review.gluster.org/6737
Reviewed-by: Kaleb KEITHLEY 
Tested-by: Gluster Build System

cluster/dht: Make sure loc has gfid

2014-01-13T12:58:45+00:00

Problem:
In some code paths neither loc->gfid nor loc->inode->gfid
is populated which leads to EINVAL for linkfile setattr
in dht_linkfile_attr_heal.

Fix:
Populate loc->gfid before dht_linkfile_attr_heal.

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

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

2013-12-24T09:53:36+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 
Reviewed-on: http://review.gluster.org/6588

tests: Change 'volume create' to 'volume create force'

2013-11-27T05:39:30+00:00

Using 'force' when creating volumes prevents errors when creating
bricks in the root partition.
This fixes test bug-823081.t for bug-962226

Change-Id: I210ffda6bdc2cced4bd54755a2b44fdfd05b813b
Original-author: John Smith 
BUG: 962226
Signed-off-by: John Smith 
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/6356
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

glusterd: changes in 'volume create' behaviour

2013-11-27T05:39:16+00:00

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

Note: This patch is needed by oVirt's Gluster Integration Project

BUG: 948729
Change-Id: I7a9d7c36b7e15269f95637cd9061abac6f8a97de
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/6355
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

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

2013-11-20T06:11:13+00:00

Change-Id: Id93b6755b9a71044a7ed90ac9c779121160a75e0
BUG: 1030208
Signed-off-by: Vijaykumar M 
Reviewed-on: http://review.gluster.org/6271
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

cluster/dht: Treat migration failures due to space constraints as skipped

2013-09-20T06:39:40+00:00

Currently rebalance/remove-brick op's display migration failed count even
for files which failed due to space issues (not enough space for file, or
migration leading to cluster imbalance)

These will now be counted as skipped, and rebalance/remove-brick status
will display the additional counter

BUG: 989846
Change-Id: I4efa7ce69dd43680ff47181afed0c561954c5080
Signed-off-by: shishir gowda 
Reviewed-on: http://review.gluster.org/5977
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

cli: Fix 'status all' xml output when volumes are not started

2013-09-19T17:29:42+00:00

 Backport of 7d9bc0d21408c31651a65a6ec0e67c3b8acd0fde from master

CLI now only outputs one XML document for 'status all' only containing
those volumes which are started.

BUG: 1004218
Change-Id: I119ac40282380886b46a09fd9a19d35115fd869d
Signed-off-by: Kaushal M 
Reviewed-on: http://review.gluster.org/5970
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

tests: Remove grep process entries from pidgrep

2013-09-15T23:16:27+00:00

Problem:
We were picking process with lowest pid from ps|grep
result. However, lowest pid need not be oldest process
as recycling of PIDs can take place.

Solution:
Removed grep process entries from ps entries using
grep -v grep.

Change-Id: I2b9687a05a34cf6358f773183770d69a3fb9eb10
BUG: 858488
Signed-off-by: Raghavendra Talur 
Reviewed-on: http://review.gluster.org/5930
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

mgmt/glusterd: Update sub_count on remove brick

2013-09-13T16:51:03+00:00

Change-Id: I7c17de39da03c6b2764790581e097936da406695
BUG: 1002556
Signed-off-by: Vijay Bellur 
Reviewed-on: http://review.gluster.org/5902
Tested-by: Gluster Build System