glusterfs.git/xlators, branch v4.0.0rc0

protocol: utilize the version 4 xdr

2018-02-01T11:41:00+00:00

updates #384

Change-Id: Id80bf470988dbecc69779de9eb64088559cb1f6a
Signed-off-by: Amar Tumballi

glusterd: optimize glusterd import volumes code path

2018-01-31T17:58:24+00:00

In case there's a version mismatch detected for one of the volumes
glusterd was ending up with updating all the volumes which is a
overkill.

>mainline patch : https://review.gluster.org/#/c/19358/

Change-Id: I6df792db391ce3a1697cfa9260f7dbc3f59aa62d
BUG: 1540554
Signed-off-by: Atin Mukherjee 
(cherry picked from commit bb34b07fd2ec5e6c3eed4fe0cdf33479dbf5127b)

core: remove experimental xlators and associated tests

2018-01-31T17:50:48+00:00

experimental xlators removed from 4.0

> Cherry picked from 4231c40973c60999f5ef759db450d25e129ef6ba:
> Reviewed-on: https://review.gluster.org/17953
> Reviewed-by: jiffin tony Thottan 

Signed-off-by: ShyamsundarR 
Change-Id: I34419ce22ca09b7626b8f9382c377a614fd9fed8
BUG: 1539842

protocol: Remove lock recovery logic from client and server

2018-01-31T04:55:37+00:00

Change-Id: I27f5e1e34fe3eac96c7dd88e90753fb5d3d14550
BUG: 1540438
Signed-off-by: Anoop C S 
(cherry picked from commit 3e78ea991b213422fc423ff94994e1eb295569c7)

dentry fop serializer: added new server side xlator for dentry fop serialization

2018-01-30T18:36:01+00:00

Problems addressed by this xlator :

[1]. To prevent race between parallel mkdir,mkdir and lookup etc.

Fops like mkdir/create, lookup, rename, unlink, link that happen on a
particular dentry must be serialized to ensure atomicity.

Another possible case can be a fresh lookup to find existance of a path
whose gfid is not set yet. Further, storage/posix employs a ctime based
heuristic 'is_fresh_file' (interval time is less than 1 second of current
time) to check fresh-ness of file. With serialization of these two fops
(lookup & mkdir), we eliminate the race altogether.

[2]. Staleness of dentries

This causes exponential increase in traversal time for any inode in the
subtree of the directory pointed by stale dentry.

Cause :  Stale dentry is created because of following two operations:

      a. dentry creation due to inode_link, done during operations like
         lookup, mkdir, create, mknod, symlink, create and
      b. dentry unlinking due to various operations like rmdir, rename,
         unlink.

       The reason is __inode_link uses __is_dentry_cyclic, which explores
       all possible path to avoid cyclic link formation during inode
       linkage. __is_dentry_cyclic explores stale-dentry(ies) and its
       all ancestors which is increases traversing time exponentially.

Implementation : To acheive this all fops on dentry must take entry locks
before they proceed, once they have acquired locks, they perform the fop
and then release the lock.

Some documentation from email conversation:
[1] http://www.gluster.org/pipermail/gluster-devel/2015-December/047314.html

[2] http://www.gluster.org/pipermail/gluster-devel/2015-August/046428.html

With this patch, the feature is optional, enable it by running:

 `gluster volume set $volname features.sdfs enable`

Also the feature is tested for a month without issues in the
experiemental branch for all the regression.

Change-Id: I6e80ba3cabfa6facd5dda63bd482b9bf18b6b79b
Fixes: #397
Signed-off-by: Sakshi Bansal 
Signed-off-by: Amar Tumballi 
Signed-off-by: Sunny Kumar

features/error-gen: update volume options for GD2

2018-01-23T04:07:41+00:00

Updates #302

Change-Id: I8d04bb4f46b1e53a8d176a75da2382fdbf0cfc6f
Signed-off-by: Atin Mukherjee

performance/read-ahead: volume option fixes for GD2

2018-01-22T15:59:42+00:00

Updates #302

Change-Id: I842ab746502bc4ff3b312ee19f397a6177edc6f7
Signed-off-by: Csaba Henk

protocol/server: Fix "auth-path" in options table

2018-01-22T11:19:16+00:00

Options set will crash the brick with glusterd2.
glusterd used to set "auth-path" during volfile
generation. With glusterd2, it should come from
options table.

Updates: #302
Change-Id: Ie41a17779c185b87ace7e0bce0d0ba594b415a75
Signed-off-by: Kotresh HR

performance/write-behind: volume option fixes for GD2

2018-01-22T10:18:08+00:00

Updates #302

Change-Id: I2ade3dc4aef4da619c5b64058872594f0f1e004f
Signed-off-by: Csaba Henk

libgfapi: Add new api for supporting mandatory-locks

2018-01-22T09:54:02+00:00

The current API for byte-range locks [glfs_posix_lock()] doesn't
allow applications to specify whether it is advisory or mandatory
type locks. This particular change is to introduce an extended
byte-range lock API with an additional argument for including
the byte-range lock mode to be one among advisory(default) or
mandatory. Patch also includes a gfapi test case which make use
of this new api to acquire mandatory locks.

Ref: https://github.com/gluster/glusterfs-specs/blob/master/done/GlusterFS%203.8/Mandatory%20Locks.md

Change-Id: Ia09042c755d891895d96da857321abc4ce03e20c
Updates #393
Signed-off-by: Anoop C S