glusterfs.git, branch v3.7.4

features/shard: Fix unlink failure due to non-existent shard(s)

2015-08-31T15:09:47+00:00

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

Unlink of a sharded file with holes was leading to EINVAL errors
because it was being wound on non-existent shards (those blocks that
fall in the hole region). loc->inode was NULL in these cases and
dht_unlink used to fail the FOP with EINVAL for failure to fetch
cached subvol for the inode.

The fix involves winding unlink on only those shards whose corresponding
inodes exist in memory.

Change-Id: I1e5d492a2e60491601da23f64a5d0089e536b305
BUG: 1258353
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/12061
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System

cli: on error invoke cli_cmd_broadcast_response function in separate thread

2015-08-31T15:04:08+00:00

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

There is a problem in current CLI framework
CLI holds the lock when processing command.
When processing quota list command, below sequence of steps executed in the
same thread and causing deadlock

1) CLI holds the lock
2) Send rpc_clnt_submit request to quotad for quota usage
3) If quotad is down, rpc_clnt_submit invokes cbk function with error
4) cbk function cli_quotad_getlimit_cbk tries to hold lock to broadcast
   the results and hangs, because same thread has already holding the lock

This patch fixes the problem by creating seperate thread for
broadcasting the result

> Change-Id: I53be006eadf6aaf348083d9168535530d70a8ab3
> BUG: 1242819
> Signed-off-by: vmallika 

Change-Id: Ic3c651c143e4143cfb4542d99b4856e582022e36
BUG: 1257881
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/12038
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Kaushal M

afr: modify afr_txn_nothing_failed()

2015-08-31T15:03:09+00:00

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

In an AFR transaction, we need to consider something as failed only if the
failure (either in the pre-op or the FOP phase) occurs on the bricks on which a
transaction lock was obtained.

Without this, we would end up considering the transaction as failure even on the
bricks on which the lock was not obtained, resulting in unnecessary fsyncs
during the post-op phase of every write transaction for non-appending writes.

Change-Id: Iee79e5d85dc7b4c41459d8bdd04a8454bdaf9a9d
BUG: 1255698
Signed-off-by: Ravishankar N 
Reviewed-on: http://review.gluster.org/11985
Tested-by: Gluster Build System 
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: NetBSD Build System

tests: rebasing bad tests from mainline branch to release-3.7 branch

2015-08-31T14:43:53+00:00

Currently mainline and release-3.7 branch not having same bad tests.
So bad tests which are bypassing in mainline still failing in
release-3.7 branch.
Rebasing all bad test from mainline branch to release-3.7 branch.

Change-Id: I2d4b9d1d3c1f37dcdfb092ca0d9c552bf1ddbef7
BUG: 1258344
Signed-off-by: Gaurav Kumar Garg 
Reviewed-on: http://review.gluster.org/12056
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

marker: preserve previous dirty flag during update txn

2015-08-31T11:14:44+00:00

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

In case if dir has become dirty because of crash,
this dirty flag on disk was getting reset in the
next update txn.

This patch now gets the dirty flag before setting
in the update txn and it the value is dirty, it keeps
the flag dirty, so that inspect_directory can fix the
dirty dir

> Change-Id: Iab2c343dbe19bd3b291adbfeebe6d9785b6bb9e3
> BUG: 1251454
> Signed-off-by: vmallika 

Change-Id: I10b81e5c0d9ffa00082171e295199d924a81ee0e
BUG: 1257441
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/12037
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Kaushal M

protocol/server : porting missing gf_log's to gf_msg

2015-08-31T09:45:09+00:00

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

Cherry-picked form commit a26dbb38acdb2ec5fe16068caee189709faae76e
> Change-Id: I8818931fafea3c013551a5de23a9f77c81164841
> BUG: 1252808
> Signed-off-by: Manikandan Selvaganesh 
> Reviewed-on: http://review.gluster.org/11895
> Tested-by: NetBSD Build System 
> Reviewed-by: Raghavendra G 

Change-Id: I8818931fafea3c013551a5de23a9f77c81164841
BUG: 1257193
Signed-off-by: Manikandan Selvaganesh 
Reviewed-on: http://review.gluster.org/12018
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Raghavendra G

features/shard: Fix permission issues

2015-08-31T09:31:10+00:00

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

This patch does the following:
* reverts commit b467af0e99b39ef708420d3f7f6696b0ca618512
* changes ownership on shards under /.shard to be root:root
* makes readv, writev, [f]truncate, rename, and unlink fops
  to perform operations on files under /.shard with
  frame->root->{uid,gid} as 0.

This would ensure that a [f]setattr on a sharded file
does not need to be called on all the shards associated with it.

Change-Id: I50d8533bd2b769a4dfe8cd1b49bdcfc117a7e660
BUG: 1253151
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/12052
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System

tests: Mark bug-1238706-daemons-stop-on-peer-cleanup.t as bad

2015-08-31T06:33:04+00:00

backport of http://review.gluster.org/#/c/12036/

This test fails frequently. Use bug number 1257792 when you
move this test out of bad_tests.

Change-Id: Ib65f22096dc9af131c4d2f38b59a857c549a674a
BUG: 1258306
Signed-off-by: Raghavendra Talur 
Reviewed-on: http://review.gluster.org/12036
Reviewed-by: Atin Mukherjee 
Tested-by: NetBSD Build System 
Reviewed-by: Gaurav Kumar Garg 
Reviewed-on: http://review.gluster.org/12050
Reviewed-by: Ravishankar N 
Reviewed-by: Vijay Bellur 
Tested-by: Gluster Build System

features/shard: Fix size update for writes at hole region

2015-08-30T06:51:50+00:00

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

Change-Id: I4b6e9101ccb881d3d285704902484e1e89ccaceb
BUG: 1257204
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/12026
Tested-by: NetBSD Build System 
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Gluster Build System

ec : trusted.ec.version xattr of all root directories of all bricks should be same.

2015-08-30T05:54:44+00:00

Problem:
After replacing the brick using "replace-brick" command and running "heal
full", the version of the root directory of the newly added brick is not
getting healed. heal starts running on the dentries of the root but does not
run on root directory.

Solution:
Run heal on root directory.

> Change-Id: Ifd42a3fb341b049c895817e892e5b484a5aa6f80
> BUG: 1243382
> Signed-off-by: Ashish Pandey 
> Reviewed-on: http://review.gluster.org/11676
> Reviewed-by: Pranith Kumar Karampuri 
> Tested-by: NetBSD Build System 

Change-Id: Ifd42a3fb341b049c895817e892e5b484a5aa6f80
BUG: 1243384
Signed-off-by: Ashish Pandey 
Reviewed-on: http://review.gluster.org/11755
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Pranith Kumar Karampuri