glusterfs.git/xlators/cluster/dht/src, branch v3.7.5

dht/rebalance: fix mem-leak in rebalance

2015-10-06T11:10:19+00:00

Change-Id: I37faf983fc02996541f3d96a17cb2a2c2cdb6781
BUG: 1261234
Reviewed-on: http://review.gluster.org/12235
Reviewed-by: Raghavendra G 
Tested-by: Raghavendra G 
Signed-off-by: Susant Palai 
Reviewed-on: http://review.gluster.org/12296

fd: Do fd_bind on successful open

2015-10-06T06:11:02+00:00

- fd_unref should decrement fd->inode->fd_count only if it is present in the
inode's fd list.
- successful open/opendir should perform fd_bind.

 >Change-Id: I81dd04f330e2fee86369a6dc7147af44f3d49169
 >BUG: 1207735
 >Signed-off-by: Pranith Kumar K 
 >Reviewed-on: http://review.gluster.org/11044
 >Reviewed-by: Anoop C S 
 >Tested-by: NetBSD Build System 
 >Tested-by: Gluster Build System 
 >Reviewed-by: Raghavendra G 

BUG: 1259697
Change-Id: I73b79dd3519aa085fb84dde74b321511cbccce1a
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/12100
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Raghavendra G

glusterd, dht: volume set for use-readdirp in dht

2015-10-05T06:49:38+00:00

 >Change-Id: Icab246b1d02808864d878d949fa56f9f889b538a
 >BUG: 1265677
 >Signed-off-by: Pranith Kumar K 
 >Reviewed-on: http://review.gluster.org/12221
 >Tested-by: NetBSD Build System 
 >Tested-by: Gluster Build System 
 >Reviewed-by: Raghavendra G 
 >Reviewed-by: Raghavendra Bhat 
 >Reviewed-by: Kaushal M 
 >(cherry picked from commit 059db0254f5670a34f1a928155c0c7d1cd03b53a)

Change-Id: Ifc46ed08fc10b32f5e814aa09c155e11e8c93138
BUG: 1267822
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/12269
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Raghavendra G

cluster/dht : FOP handling during file migration

2015-09-29T05:37:11+00:00

An earlier patch introduced a bug in the FOP migration
code. Fixed the issue.

Change-Id: Ib7d8d3f54ddd455b7f53b0b2e3a82a9e942ba1f9
BUG: 1266872
Signed-off-by: N Balachandran 
Reviewed-on: http://review.gluster.org/12238
Reviewed-by: Raghavendra G 
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System

cluster/tier: Handle FOPs on files being migrated

2015-09-25T12:36:12+00:00

Determine which DHT level is responsible for
handling fops on a file undergoing migration based
on the name of the the linkto xattr set on the file
 being migrated and process accordingly.

Change-Id: I82772e39314d4fe7f2ba0dcf22de0c6a374ee139
BUG: 1265892
Signed-off-by: N Balachandran 
> Reviewed-on: http://review.gluster.org/12090
> Tested-by: NetBSD Build System 
> Tested-by: Gluster Build System 
> Reviewed-by: Raghavendra G 
(cherry picked from commit 470869a954c17f32a3ba43ccda7442f82c0da6b2)
Reviewed-on: http://review.gluster.org/12224
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Dan Lambright 
Tested-by: Dan Lambright

cluster/dht: Reset source file mode bits on migration failure

2015-09-21T11:29:18+00:00

DHT rebalance uses the sgid and sticky bits to indicate
that a file is being migrated. These were not removed if
the file migration failed.
The fix resets these bits to the original values.

>Change-Id: I9801bfc0bd80c0800251ccd66c1c91a51cffd909
>Signed-off-by: Nithya Balachandran 
>Reviewed-on: http://review.gluster.org/11454
>Tested-by: NetBSD Build System 
>Tested-by: Gluster Build System 
>Reviewed-by: Raghavendra G 

Change-Id: Ia701687819ee7130d6abebad84feb2ee879b7ab2
BUG: 1262700
Signed-off-by: N Balachandran 
Reviewed-on: http://review.gluster.org/12167
Tested-by: Gluster Build System 
Reviewed-by: Raghavendra G

cluster/dht : Propagate op_errno on failure

2015-09-21T11:28:58+00:00

Fixed issue where dht_selfheal_layout_lock_cbk does not propagate
the op_errno.

>Change-Id: I0b968339db65d2969e36e64407eeb724cc6516bd
>BUG: 1262438
>Signed-off-by: Nithya Balachandran 
>Reviewed-on: http://review.gluster.org/12165
>Tested-by: NetBSD Build System 
>Tested-by: Gluster Build System 
>Reviewed-by: Raghavendra G 

(cherry picked from commit 2ec8ea8769e943d3987dd80f8f6937359bcccf34)
Signed-off-by: Nithya Balachandran 

Change-Id: I6b744be71c87737f0f35fe70c3ffbf391bb1a153
BUG: 1263191
Reviewed-on: http://review.gluster.org/12178
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Raghavendra G

cluster/tier: Fixed a crash in tiering

2015-09-16T18:43:57+00:00

This is a backport of 12179

An incorrect check was causing the arguments to
the promote thread to be cleared before the thread
was done with them. This caused the process to crash
when it tried to dereference a NULL pointer.

> Change-Id: I8348309ef4dad33b7f648c7a2c2703487e401269
> BUG: 1263204
> Signed-off-by: Nithya Balachandran 
> Reviewed-on: http://review.gluster.org/12179
> Tested-by: NetBSD Build System 
> Reviewed-by: Dan Lambright 
> Reviewed-by: Joseph Fernandes
Signed-off-by: Dan Lambright 

Change-Id: I5cd4cb9978fc9d3a74f69ef75474fc3b593aadf0
BUG: 1263746
Reviewed-on: http://review.gluster.org/12187
Reviewed-by: N Balachandran 
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Tested-by: Dan Lambright

cluster/tier do not flag migration error on already migrated file

2015-09-16T17:31:42+00:00

In some cases a brick will try to migrate a file that has already
been migrated. This is a legal case, e.g. when both bricks
are replica pairs.

Change-Id: If2578b947014cbbdfb3c6591db9044d6b1d92774
BUG: 1262408
Signed-off-by: Dan Lambright 
Reviewed-on: http://review.gluster.org/12186
Tested-by: NetBSD Build System 
Reviewed-by: Joseph Fernandes
Tested-by: Gluster Build System

dht/remove-brick: Avoid data loss for hard link migration

2015-09-14T05:46:58+00:00

Problem: If the hashed subvol of a file has reached cluster.min-free-disk,
for a create opertaion a linkto file will be created on the hashed and
the data file will be created on some other brick.

For creation of the linkfile we populate the dictionary with linkto key
and value as the cached subvol. After successful linkto file creation,
the linkto-key-value pair is not deleted form the dictionary and hence,
the data file will also have linkto xattr which points to itself.This looks
something like this.

  client-0                                    client-1
-------T file                               rwx------file
linkto.xattr=client-1                       linkto.xattr=client-1

Now coming to the data loss part. Hardlink migration highly depend on this
linkto xattr on the data file. This value should be the new hashed subvol
of the first hardlink encountered post fix-layout. But when it tries to
read the linkto xattr it gets the same target as where it is sitting.

Now the source and destination are same for migration. At the end of
migration the source file is truncated and deleted, which in this case
is the destination and also the only data file it self resulting in
data loss.

BUG: 1262197
Change-Id: I5338a5704ac60ca9afb278977e178319266a0cc0
Signed-off-by: Susant Palai 
Reviewed-on: http://review.gluster.org/12105
Reviewed-by: N Balachandran 
Tested-by: NetBSD Build System 
Reviewed-by: Raghavendra G 
Signed-off-by: Susant Palai 
Reviewed-on: http://review.gluster.org/12156
Tested-by: Gluster Build System