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

cluster/dht: avoid mknod on decommissioned brick

2015-08-27T13:27:54+00:00

BUG: 1256702
Change-Id: I0795720cb77a9c77e608f34fbb69574fd2acb542
Signed-off-by: Susant Palai 
Reviewed-on: http://review.gluster.org/11998
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Raghavendra G 
Signed-off-by: Susant Palai 
Reviewed-on: http://review.gluster.org/12024

dht: block/handle create op falling to decommissioned brick

2015-08-27T04:55:56+00:00

Problem:
Post remove-brick start till commit phase, the client layout
may not be in sync with disk layout because of lack of lookup.
Hence,a create call may fall on the decommissioned brick.

Solution:
Will acquire a lock on hashed subvol. So that a fix-layout or
selfheal can not step on layout while reading the layout.

Even if we read a layout before remove-brick fix-layout and the
file falls on the decommissioned brick, the file should be
migrated to a new brick as per the fix-layout.

BUG: 1256283
Change-Id: I3ef1adaf20dfb9524396a3648d1a664464eda8c1
Signed-off-by: Susant Palai 
Reviewed-on: http://review.gluster.org/11260
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Raghavendra G 
Signed-off-by: Susant Palai 
Reviewed-on: http://review.gluster.org/12001

dht/tiering : create new dictionary during migration

2015-08-20T06:38:51+00:00

To avoid setting wrong xattr during creating link file

Back port of:
>Change-Id: Iad8de3521eae17e510035ed42e3e01933d647096
>BUG: 1250828
>Signed-off-by: Mohammed Rafi KC 
>Reviewed-on: http://review.gluster.org/11838
>Reviewed-by: N Balachandran 
>Tested-by: Gluster Build System 
>Reviewed-by: Dan Lambright 
>Reviewed-by: Raghavendra G 

(cherry picked from commit a3faffb259d5288907fac33a2822a8f61c3e86fe)

Change-Id: I76ef168cd881c8fd828283a1ae70ed251fc44aaa
BUG: 1254438
Signed-off-by: Mohammed Rafi KC 
Reviewed-on: http://review.gluster.org/11945
Reviewed-by: Dan Lambright 
Tested-by: Dan Lambright

dht/tier :rename fails with EBUSY

2015-08-20T02:44:07+00:00

When the files was in hot tier and the look up was done already, then
hashed and cached subvolume will be hot-tier. Once the file is moved
from hot-tier to cold-tier, then subsequent lookup will send a
revalidate lookup to hot-tier and it will find out that the file was
actually moved and there is only link in the cached subvolume. So dht
will return an ESTALE to fuse. Upon receiving ESTALE for a lookup, fuse
will create a new inode and sent a fresh lookup. This lookup will be
successful, and it will locate the file properly. Then fuse try to link
the inode, but the older inode was already there in inmemory inode cache
with same gfid and that is also shared with fuse kernal. So inode_link
will return the older ionode itself. So the subsequent rename fop will
come to gluster with the older inode. From dht_rename, we will take a
lock on the inode and after successful inodelk on inode dht will send
lookup before creating a link. this lookup will again find out that the
file is a link file, and then dht will think that file is
migrating/migrated in the mean time, and will send EBUSY.

Back port of :
>Change-Id: Ib3a01e5b1d7f64514b04bb6234026d049f082679
>BUG: 1248306
>Signed-off-by: Mohammed Rafi KC 
>Reviewed-on: http://review.gluster.org/11768
>Tested-by: Gluster Build System 
>Reviewed-by: Raghavendra G 
>Reviewed-by: Dan Lambright 
>Tested-by: NetBSD Build System 
>Tested-by: Dan Lambright 

(cherry picked from commit 0ad26041fbf65ab36856a0ad178c32e51bf87319)

Change-Id: I1278a2c2ccc2cadcbe147db836f0526f079f6038
BUG: 1254437
Signed-off-by: Mohammed Rafi KC 
Reviewed-on: http://review.gluster.org/11944
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Dan Lambright 
Tested-by: Dan Lambright

cluster/tier : Use dht_* versions for xlator_fops

2015-08-19T08:14:12+00:00

The tier xlator was using the default_* versions
for some xlator_fops. Changed to use the dht_*
versions for all xlator_fops

Change-Id: I8252fb3911b8a48a55e9eee42b89bd66bbacf799
BUG: 1254468
Signed-off-by: N Balachandran 
(cherry picked from commit 0c20107a60726804030f98a7f79b94c677e6a7b6)
Reviewed-on: http://review.gluster.org/11951
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Dan Lambright 
Tested-by: Dan Lambright

cluster/tier: fix demotion when cold tier is EC

2015-08-12T16:09:28+00:00

This is a backport of 11855.

We did not set the gfid in the loc structure in tier demotion. EC
has a sanity check which fails FOPs when the loc gfid mismatches
with the file attribute. When the FOP failed demotion was aborted.

> Change-Id: I69022c9ccb135b86e1feea93b01801b6a4100509
> BUG: 1251121
> Signed-off-by: Dan Lambright 

Change-Id: I266d554e3e0a2ff024a5ba3a7e9ca40866688eae
BUG: 1252907
Signed-off-by: Dan Lambright 
Reviewed-on: http://review.gluster.org/11901
Reviewed-by: mohammed rafi  kc 
Tested-by: NetBSD Build System

dht: Adding log messages to the new logging framework

2015-07-27T07:21:48+00:00

        Backported from: http://review.gluster.org/10021

> Change-Id: Ib3bb61c5223f409c23c68100f3fe884918d2dc3f
> BUG: 1194640
> Reviewed-on: http://review.gluster.org/10021
> Reviewed-by: N Balachandran 
> Reviewed-by: Joseph Fernandes 
> Tested-by: Joseph Fernandes 
> Reviewed-by: Dan Lambright 
> Reviewed-by: Raghavendra G 
> Tested-by: Raghavendra G 
> Signed-off-by: arao 

BUG: 1217722
Change-Id: Ide79c6c1e6a466fb52f955c90a2b22711bec794a
Signed-off-by: arao 
Signed-off-by: Anusha Rao 
Reviewed-on: http://review.gluster.org/11350
Tested-by: NetBSD Build System 
Reviewed-by: Raghavendra G 
Tested-by: Gluster Build System

dht: send lookup even for fd based operations during rebalance

2015-07-24T07:22:15+00:00

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

Problem:
dht_rebalance_inprogress_task() was not sending lookups to the
destination subvolume for a file undergoing writes during rebalance. Due to
this, afr was not able to populate the read_subvol and failed the write
with EIO.

Fix:
Send lookup for fd based operations as well.

Thanks to Raghavendra G for helping with the RCA.

Change-Id: Iaa427666328109bbdf228876e62c13b75b7df88e
BUG: 1245934
Signed-off-by: Ravishankar N 
Reviewed-on: http://review.gluster.org/11744
Tested-by: Gluster Build System 
Reviewed-by: N Balachandran 
Reviewed-by: Raghavendra G 
Tested-by: NetBSD Build System

features/shard: Use xattrop (as opposed to setxattr) for updates to size xattr

2015-07-22T06:25:51+00:00

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

Change-Id: I9effecbb1296d11cf1629b5e5cc38192f84cfcb3
BUG: 1243655
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/11689
Tested-by: Gluster Build System 
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Pranith Kumar Karampuri

syncop: Include iatt to 'syncop_link' args

2015-07-15T15:08:30+00:00

Include iatt to 'syncop_link' args to fetch proper attributes of
the newly linked inode.

This is backport of the below fix -
http://review.gluster.org/11611

Change-Id: If6b92961bd7a89add3791ed3a9b494087348b492
BUG: 1243408
Reviewed-on: http://review.gluster.org/11611
Reviewed-by: Shyamsundar Ranganathan 
Reviewed-by: Kaleb KEITHLEY 
Signed-off-by: Soumya Koduri 
Reviewed-on: http://review.gluster.org/11677
Tested-by: Gluster Build System