glusterfs.git/xlators, branch v3.12.0

feature/posix: Enabled gfid2path by default

2017-08-29T20:09:32+00:00

Enable gfid2path feature by default. The basic
performance tests are carried out and it doesn't
show significant depreciation. The results are
updated in issue.

Updates: #139
Change-Id: I5f1949a608d0827018ef9d548d5d69f3bb7744fd
> Signed-off-by: Kotresh HR 
> Reviewed-on: https://review.gluster.org/17950
> Smoke: Gluster Build System 
> CentOS-regression: Gluster Build System 
> Reviewed-by: Aravinda VK 
> Reviewed-by: Amar Tumballi 
(cherry picked from commit 3ec63650bb7fd874a5013e7be4a2def3b519c9b2)
Reviewed-on: https://review.gluster.org/18133
Reviewed-by: Amar Tumballi 
Smoke: Gluster Build System 
Tested-by: Shyamsundar Ranganathan 
CentOS-regression: Gluster Build System 
Reviewed-by: Shyamsundar Ranganathan

glusterd: replace-brick executing successfully when quorum does not met

2017-08-29T12:39:52+00:00

Problem:
replace-brick command on a setup where quorum does not met executing
successfully.

Fix:
With the fix glusterd is validating whether server is in quorum or not
during replace-brick staging

>Reviewed-on: https://review.gluster.org/18068
>Smoke: Gluster Build System 
>CentOS-regression: Gluster Build System 
>Reviewed-by: Atin Mukherjee 

Change-Id: I8017154bb62bdcc6c6490e720ecfe9cde090c161
BUG: 1486110
Signed-off-by: Gaurav Yadav 
Reviewed-on: https://review.gluster.org/18125
Smoke: Gluster Build System 
Reviewed-by: Atin Mukherjee 
Reviewed-by: Prashanth Pai 
CentOS-regression: Gluster Build System

glusterd: disable rpc_clnt_t after relalance process disconnection

2017-08-25T19:00:50+00:00

Problem:
glusterd continues to connect to rebalance process even after
the socket connection has disconnected.

Solution:
rpc_clnt_disable() disables the rpc_clnt_t object and disarms
all relevant timers and drops refs to the rpc_clnt_t object
and the transport as well.

>Reviewed-on: https://review.gluster.org/18114
>Reviewed-by: MOHIT AGRAWAL 
>Tested-by: Atin Mukherjee 
>Reviewed-by: Atin Mukherjee 
>Smoke: Gluster Build System 
>CentOS-regression: Gluster Build System 
>(cherry picked from commit a894d44427649e99d4344a241dc2f9d584a9a691)

Change-Id: I981d6f1cc0087037f1927062c2770a4d5026a619
BUG: 1484885
Signed-off-by: Milind Changire 
Reviewed-on: https://review.gluster.org/18117
Tested-by: Atin Mukherjee 
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Shyamsundar Ranganathan

uss/svc: Send the first lookup to the normal graph

2017-08-21T14:29:24+00:00

When parent inode is not looked up before, the inode type
won't be set. In this scenario we should send the lookup
to the normal graph first.

Backport of>
>Change-Id: I5d3e53f5c1c33a17be32204f3114749d9b1e6db8
>BUG: 1480591
>Signed-off-by: Mohammed Rafi KC 
>Reviewed-on: https://review.gluster.org/18028
>Smoke: Gluster Build System 
>Reviewed-by: Raghavendra Bhat 
>CentOS-regression: Gluster Build System 
>Reviewed-by: soumya k 

(cherry picked from commit d396d358d4f0cfe87693179cfd13eb2a84ce62c2)

Change-Id: I5d3e53f5c1c33a17be32204f3114749d9b1e6db8
BUG: 1481931
Signed-off-by: Mohammed Rafi KC 
Reviewed-on: https://review.gluster.org/18042
Smoke: Gluster Build System 
Reviewed-by: Amar Tumballi 
CentOS-regression: Gluster Build System 
Reviewed-by: Shyamsundar Ranganathan

glusterd : glusterd fails to start when peer's network interface is down

2017-08-21T14:28:58+00:00

Problem:
glusterd fails to start on nodes where glusterd tries to come up even
before network is up.

Fix:
On startup glusterd tries to resolve brick path which is based on
hostname/ip, but in the above scenario when network interface is not
up, glusterd is not able to resolve the brick path using ip_address or
hostname With this fix glusterd will use UUID to resolve brick path.

>Reviewed-on: https://review.gluster.org/17813
>Smoke: Gluster Build System 
>Reviewed-by: Prashanth Pai 
>CentOS-regression: Gluster Build System 
>Reviewed-by: Atin Mukherjee 
>(cherry picked from commit 1477fa442a733d7b1a5ea74884cac8f29fbe7e6a)

Change-Id: Icfa7b2652417135530479d0aa4e2a82b0476f710
BUG: 1482835
Signed-off-by: Gaurav Yadav 
Reviewed-on: https://review.gluster.org/18061
Tested-by: Atin Mukherjee 
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Shyamsundar Ranganathan

glusterd: disallow volume specific options to be set with all as volume name

2017-08-21T14:28:10+00:00

All the .validate_fn defined in volume map entry table refers to volinfo
object. And if we end up in trying to set a volume level option cluster
wide glusterd results into a crash.

>Reviewed-on: https://review.gluster.org/18052
>Smoke: Gluster Build System 
>Reviewed-by: Prashanth Pai 
>Reviewed-by: mohammed rafi  kc 
>Reviewed-by: Gaurav Yadav 
>CentOS-regression: Gluster Build System 
>(cherry picked from commit 01abf7ee37702407403afcf9aa6c9019a0316e1d)

Change-Id: I7c877aee0ff5c8c1d8c95662fdc8c8923355ae7b
BUG: 1482804
Signed-off-by: Atin Mukherjee 
Reviewed-on: https://review.gluster.org/18060
Reviewed-by: Prashanth Pai 
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Shyamsundar Ranganathan

cluster/dht: Reorder dir operations in gf_defrag_fix_layout

2017-08-21T14:27:11+00:00

Earlier, rebalance performed a fix-layout on a directory
before healing its subdirectories. If there were a lot of
subdirs, it could take a while before all subdirs were
created on the newly added bricks. As dht_readdirp only lists
dirs from their hashed subvol, those dirs which hashed to
the newly added bricks but were not yet created on them were
not listed.

Now, the child dirs are listed and processed before the layout
of the parent is fixed. This introduces a change in behaviour
where files in subdirs are migrated before those in parent
directories.

Credit: Shyam 
Github issue: #239

> BUG: 1248393
> Signed-off-by: N Balachandran 
> Reviewed-on: https://review.gluster.org/18045
> Smoke: Gluster Build System 
> CentOS-regression: Gluster Build System 
> Reviewed-by: Raghavendra G 
(cherry picked from commit 96b33b4b278391ca8a7755cf274931d4f1808cb5)
Change-Id: I8ae7f24a510754cd8d1b31e5d608bcf1928599e2
BUG: 1483402
Signed-off-by: N Balachandran 
Reviewed-on: https://review.gluster.org/18071
Smoke: Gluster Build System 
Reviewed-by: Raghavendra G 
CentOS-regression: Gluster Build System

mgmt/glusterd: Provide more information in command message

2017-08-12T13:38:51+00:00

Problem:
When more than one bricks are present on the same node,
while creating a volume, we get a warning message that
the setup is not optimal. We need to add more information
in this error/warning.

Solution:
Add following line in current message.
Bricks should be on different nodes to have best fault
tolerant configuration.

>Change-Id: Ica72bd6e68dff7e41c37617f3b775a981fa40c69
>BUG: 1480099
>Signed-off-by: Ashish Pandey 
>Reviewed-on: https://review.gluster.org/18014
>CentOS-regression: Gluster Build System 
>Smoke: Gluster Build System 
>Reviewed-by: Atin Mukherjee 
>Signed-off-by: Ashish Pandey 

Change-Id: Ica72bd6e68dff7e41c37617f3b775a981fa40c69
BUG: 1480448
Signed-off-by: Ashish Pandey 
Reviewed-on: https://review.gluster.org/18022
Reviewed-by: Atin Mukherjee 
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System

glusterd: Gluster should keep PID file in correct location

2017-08-12T13:38:30+00:00

Currently Gluster keeps process pid information of all the daemons
and brick processes in Gluster configuration file directory
(ie., /var/lib/glusterd/*).

These pid files should be seperate from configuration files.
Deletion of the configuration file directory might result into serious problems.
Also, /var/run/gluster is the default placeholder directory for pid files.

So, with this fix Gluster will keep all process pid information of all
processes in /var/run/gluster/* directory.

> BUG: 1258561
> Signed-off-by: Gaurav Kumar Garg 
> Signed-off-by: Saravanakumar Arumugam 
> Reviewed-on: https://review.gluster.org/13580
> Tested-by: MOHIT AGRAWAL 
> Smoke: Gluster Build System 
> CentOS-regression: Gluster Build System 
> Reviewed-by: Atin Mukherjee 
> cherry pick from commit 220d406ad13d840e950eef001a2b36f87570058d

BUG: 1480459
Change-Id: Idb09e3fccb6a7355fbac1df31082637c8d7ab5b4
Signed-off-by: Mohit Agrawal 
Reviewed-on: https://review.gluster.org/18023
Reviewed-by: Atin Mukherjee 
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System

storage/posix: Use the ret value of posix_gfid_heal()

2017-08-12T13:37:58+00:00

... to make the change in commit acf8cfdf truly useful.

Without this, a race between entry creation fops and lookup
at posix layer can cause lookups to fail with ENODATA, as
opposed to ENOENT.

Backport of:
> Change-Id: I44a226872283a25f1f4812f03f68921c5eb335bb
> Reviewed-on: https://review.gluster.org/17821
> BUG: 1472758
> cherry-picked from 669868d23eaeba42809fca7be134137c607d64ed

Change-Id: I44a226872283a25f1f4812f03f68921c5eb335bb
BUG: 1479717
Signed-off-by: Krutika Dhananjay 
Reviewed-on: https://review.gluster.org/18010
CentOS-regression: Gluster Build System 
Reviewed-by: Raghavendra Bhat 
Smoke: Gluster Build System