glusterfs.git, branch v3.9.1

release: updated release note

2017-01-17T18:37:06+00:00

Change-Id: I6dbac83798b455b7f420962e6ff20c6d3a3007bc
BUG: 1411333
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: http://review.gluster.org/16423
NetBSD-regression: NetBSD Build System 
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System

release: add 3.9.1 release note

2017-01-17T17:02:39+00:00

Change-Id: I909b08ec3a51dc25da5a3878117f73d57fde5d86
BUG: 1411333
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: http://review.gluster.org/16418
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Smoke: Gluster Build System

ec: Invalidations in disperse volume should not update the stat

2017-01-17T14:55:46+00:00

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

Issue:
In disperse volume, the file is present across bricks, hence the stat
from one brick doesn't carry the valid size of the file. Therefore
the upcall from one brick updating the md-cache results in wrong size
being updated.

Fix:
If the notification is cache invalidation then, indicate md-cache that
the attributes is invalid.

>Reviewed-on: http://review.gluster.org/16329
>Smoke: Gluster Build System 
>NetBSD-regression: NetBSD Build System 
>Reviewed-by: Xavier Hernandez 
>CentOS-regression: Gluster Build System 
>Reviewed-by: Pranith Kumar Karampuri 
(cherry picked from commit 95d07a3d2d68805d93d36a447436e27c48777939)

BUG: 1410688
Change-Id: Id89d2283478e70b62b435a8891fffc86d2be8cb2
Signed-off-by: Poornima G 
Reviewed-on: http://review.gluster.org/16341
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Pranith Kumar Karampuri

cluster/afr: Remove backward compatibility for locks with v1

2017-01-17T14:46:53+00:00

When we have cascading locks with same lk-owner there is a possibility for
a deadlock to happen. One example is as follows:

self-heal takes a lock in data-domain for big name with 256 chars of "aaaa...a"
and starts heal in a 3-way replication when brick-0 is offline and healing from
brick-1 to brick-2 is in progress. So this lock is active on brick-1 and
brick-2. Now brick-0 comes online and an operation wants to take full lock and
the lock is granted at brick-0 and it is waiting for lock on brick-1. As part
of entry healing it takes full locks on all the available bricks and then
proceeds with healing the entry. Now this lock will start waiting on brick-0
because some other operation already has a granted lock on it. This leads to a
deadlock. Operation is waiting for unlock on "aaaa..." by heal where as heal is
waiting for the operation to unlock on brick-0. Initially I thought this is
happening because healing is trying to take a lock on all the available bricks
instead of just the bricks that are participating in heal. But later realized
that same kind of deadlock can happen if a brick goes down after the heal
starts but comes back before it completes. So the essential problem is the
cascading locks with same lk-owner which were added for backward compatibility
with afr-v1 which can be safely removed now that versions with afr-v1 are
already EOL. This patch removes the compatibility with v1 which requires
cascading locks with same lk-owner.

In the next version we can make locking-scheme option a dummy and switch
completely to v2.

 >BUG: 1401404
 >Change-Id: Ic9afab8260f5ff4dff5329eb0429811bcb879079
 >Signed-off-by: Pranith Kumar K 
 >Reviewed-on: http://review.gluster.org/16024
 >Smoke: Gluster Build System 
 >Reviewed-by: Ravishankar N 
 >NetBSD-regression: NetBSD Build System 
 >CentOS-regression: Gluster Build System 

BUG: 1413062
Change-Id: I4f5d485d9e0646ad3dc384e5ec36682b0933c9d3
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/16413
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System

libglusterfs: fix statvfs in FreeBSD

2017-01-13T21:23:30+00:00

FreeBSD interprets statvfs' f_bsize field in a different way than Linux.

This fix modifies the value returned by statvfs() on FreeBSD to match
the expected value by Gluster.

> Change-Id: I930dab6e895671157238146d333e95874ea28a08
> BUG: 1356076
> Signed-off-by: Xavier Hernandez 
> Reviewed-on: http://review.gluster.org/16361
> Smoke: Gluster Build System 
> NetBSD-regression: NetBSD Build System 
> Reviewed-by: Kaleb KEITHLEY 
> CentOS-regression: Gluster Build System 
> Reviewed-by: Jeff Darcy 

Change-Id: I3a8e06bea7ce63d16e5569260bf9abdbced06dc1
BUG: 1411898
Signed-off-by: Xavier Hernandez 
Reviewed-on: http://review.gluster.org/16398
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Kaleb KEITHLEY 
CentOS-regression: Gluster Build System

rpm: fix glusterfs-server(%postun) scriptlet error

2017-01-13T20:16:49+00:00

While introducing the usage of the %firewalld_restart macro, the old
scriplet was not correctly removed. This causes an error to be displayed
when the RPM gets updated or uninstalled.

Cherry picked from commit e3d09359b2090c0dc9160b693969f69ecda3477c:
> Fixes: f99750b4477538cd1f97ce6340e1813202f986e2
> Change-Id: I69091d8e9e3c412dc3cb52246967eac29d2ebc90
> BUG: 1410853
> Signed-off-by: Niels de Vos 

Fixes: 60acdbd87a2c3d5bf1b199b91a7d154467fe1b79
Change-Id: I69091d8e9e3c412dc3cb52246967eac29d2ebc90
BUG: 1410854
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/16409
Reviewed-by: Kaleb KEITHLEY 
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System

cluster/afr: Do not log of split-brain when there isn't one

2017-01-13T12:38:58+00:00

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

* Even on errors like ENOENT, AFR logs split-brain after
  read-txn refresh, introduced by commit a07ddd8f.
  This can be a cause of much panic and confusion and needs to be fixed.

* Also fixed this issue in write-txns.

* Fixed afr read txns to log about split-brain only after knowing that
  there is no split-brain choice configured.

* Removed code duplication

* Fixed incorrect passing of error code in afr_write_txn_refresh_done()
  (the function was passing -0 as errno to gf_msg().

Change-Id: Ie40d2c498674a1fe8dc2c521b05e30c0bce85c02
BUG: 1412914
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/16388
Smoke: Gluster Build System 
Reviewed-by: Ravishankar N 
Reviewed-by: Pranith Kumar Karampuri 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System

mount/fuse: Fix the place where graph-switch event is logged

2017-01-13T09:29:16+00:00

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

Change-Id: I3c8577b87db02a2a6ce6159e7d04cf58a2bda0c1
BUG: 1411612
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/16365
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Raghavendra G 
CentOS-regression: Gluster Build System

afr: Avoid resetting event_gen when brick is always down

2017-01-13T08:31:12+00:00

Problem:
__afr_set_in_flight_sb_status(), which resets event_gen to zero, is
called if failed_subvols[i] is non-zero for any brick. But failed_subvols[i]
is true even if the brick was down *before* the transaction started.
Hence say if 1 brick is down in  a replica-3, every writev that comes
will trigger an inode refresh because of this resetting, as seen from
the no. of FSTATs in the profile info in the BZ.

Fix:
Reset event gen only if the brick was previously a valid read child and
the FOP failed on it the first time.

Also `s/afr_inode_read_subvol_reset/afr_inode_event_gen_reset` because
the function only resets event gen and not the data/metadata readable.

> Signed-off-by: Ravishankar N 
> Reviewed-on: http://review.gluster.org/16309
> Smoke: Gluster Build System 
> Reviewed-by: Pranith Kumar Karampuri 
> Tested-by: Pranith Kumar Karampuri 
> NetBSD-regression: NetBSD Build System 
> CentOS-regression: Gluster Build System 
(cherry picked from commit 522640be476a3f97dac932f7046f0643ec0ec2f2)

Change-Id: I603ae646cbde96995c35db77916e2ed80b602a91
BUG: 1412886
Reviewed-on: http://review.gluster.org/16385
Tested-by: Ravishankar N 
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Krutika Dhananjay 
Reviewed-by: Pranith Kumar Karampuri 
CentOS-regression: Gluster Build System

rpm: depend on firewalld-filesystem for directory ownership

2017-01-12T16:07:23+00:00

Also use the %firewalld_reload macro that is provided by the
firewalld-filesystem package.

Cherry picked from commit f99750b4477538cd1f97ce6340e1813202f986e2:
> BUG: 1410853
> Change-Id: Ibbbc18cc394f8b1e5ba74927effc41c466667479
> Signed-off-by: Niels de Vos 
> Reviewed-on: http://review.gluster.org/16351
> Smoke: Gluster Build System 
> Tested-by: Kaleb KEITHLEY 
> CentOS-regression: Gluster Build System 
> NetBSD-regression: NetBSD Build System 
> Reviewed-by: Kaleb KEITHLEY 

Change-Id: Ibbbc18cc394f8b1e5ba74927effc41c466667479
BUG: 1410854
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/16369
Reviewed-by: Kaleb KEITHLEY 
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System