glusterfs.git/xlators/mgmt/glusterd, branch v3.7.8

Revert "glusterd/afr: store afr pending xattrs as a volume option"

2016-02-08T08:18:23+00:00

This reverts commit 486b07dfc33782d27e3458659cdd6090f496ad35.

Change-Id: I2da12ef77fb01c52cae3c3b5547398b6a4d7d17e
BUG: 1293536
Signed-off-by: Pranith Kumar Karampuri 
Reviewed-on: http://review.gluster.org/13339
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System

glusterd: improve error logs for unsupported clients

2016-02-01T11:03:12+00:00

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

Change-Id: I90be46a7b25cc3efd0e61c9a145852e9027f5f64
BUG: 1302521
Signed-off-by: Atin Mukherjee 
Reviewed-on: http://review.gluster.org/11831
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Pranith Kumar Karampuri 
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Prashanth Pai 
Reviewed-by: Kaushal M 
NetBSD-regression: NetBSD Build System 
Reviewed-on: http://review.gluster.org/13305

snapd: Do not persist snapd port

2016-01-31T02:26:57+00:00

    Backport of http://review.gluster.org/#/c/13118/

Currently snapd persists the port it uses
to sign-in with glusterd, without checking
if that particular port is being used by any
other process. As a result, it might erroneously
sign out any other process using the same port.

Hence forcing snapd to ignore the persisted port,
and using a new one while coming up.

Change-Id: Ibb9ec3762aac445f03d96e85660585be4ab27bcb
BUG: 1294797
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/13119
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Pranith Kumar Karampuri 
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System

quota: start aux mount from glusterd with inet address

2016-01-22T11:27:14+00:00

This is a backport of http://review.gluster.org/#/c/13255

With below patches, quota aux mount now
uses unix domain socket to connect to
glusterd
http://review.gluster.org/#/c/12645/
http://review.gluster.org/#/c/12819/

When USS is enabled, snapd protocol client tries to
connect to glusterd with inet and fails,
because remote-host option by client process
is set to UDS file

This patch starts the aux client process from glusterd
with inet address

> Change-Id: I6967043bfd8824658ea39bfd2842591fcc3280fd
> BUG: 1299497
> Signed-off-by: vmallika 

Change-Id: Ica512aaf5c2b25f86506bd1e0d7810a8ff1f7632
BUG: 1300243
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/13267
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Atin Mukherjee

cli: Add arbiter details to volinfo xml output

2016-01-22T05:28:08+00:00

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

The followig are added:
1. "1" and
"1"

2. "0" on the brick info, like so:
127.0.0.2:/home/ravi/bricks/brick1
127.0.0.2:/home/ravi/bricks/brick1
cafa8612-d7d4-4007-beea-72ae7477f3bb
0


Also fix a bug in gluster vol info where the abiter brick was shown the
wrong brick of the cold tier after performing a tier-attach.

Change-Id: Id978325d02b04f1a08856427827320e169169810
BUG: 1300174
Signed-off-by: Ravishankar N 
Reviewed-on: http://review.gluster.org/13263
Smoke: Gluster Build System 
Reviewed-by: Anuradha Talur 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Pranith Kumar Karampuri

snapshot: Return before redundant quorum check

2016-01-20T06:57:21+00:00

    Backport of http://review.gluster.org/#/c/13260/

As of today, we don't support creation of snapshot even
if one brick is down. Hence the older quorum check is
redundant. Returning after performing the check to
see if all bricks are up.

Change-Id: I35661d05a15be0109aaae51b4fe0d5a8ca4333ad
BUG: 1299822
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/13261
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Rajesh Joseph

all: reduce "inline" usage

2016-01-18T09:02:34+00:00

There are three kinds of inline functions: plain inline, extern inline,
and static inline.  All three have been removed from .c files, except
those in "contrib" which aren't our problem.  Inlines in .h files, which
are overwhelmingly "static inline" already, have generally been left
alone.  Over time we should be able to "lower" these into .c files, but
that has to be done in a case-by-case fashion requiring more manual
effort.  This part was easy to do automatically without (as far as I can
tell) any ill effect.

In the process, several pieces of dead code were flagged by the
compiler, and were removed.

backport of Change-Id: I56a5e614735c9e0a6ee420dab949eac22e25c155,
http://review.gluster.org/11769, BUG: 1245331

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

glusterd: import/export brickinfo->uuid

2016-01-14T09:35:05+00:00

Backport of http://review.gluster.org/#/c/13047/ 

    Given a two node cluster with node N1 & N2, if a dummy node N3 is peer probed, the
    probed node N3  goes for importing volumes from the probing node (N1), but
    it still doesn't have information about the other node (N2) about its membership
    (since peer update happens post volume updates) and hence fail to update its
    brick's uuid. Post that even though N2 updates N3 about its membership the
    brick's uuid was never generated. Now as a consequence when N3 initiates a
    detach of N2, it checks whether the node to be detached has any bricks
    configured by its respective uuid which is NULL in this case and hence it goes
    ahead and removes the peer which ideally it shouldn't have (refer to
    glusterd_friend_contains_vol_bricks () for the logic)
    
    Fix is to export brick's uuid and import it at the probed node instead of
    resolving it.

Change-Id: I2d88c72175347550a45ab12aff0ae248e56baa87
BUG: 1297305
Signed-off-by: Atin Mukherjee 
Reviewed-on: http://review.gluster.org/13047
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Gaurav Kumar Garg 
Reviewed-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/13210

glusterd: register rpc notification for unix sockets

2016-01-14T07:01:15+00:00

This is a backport of http://review.gluster.org/#/c/13174/

Previously only CLI was using unix socket to connect to glusterd,
and there was no need to register rpc callback notifications.
Now auxiliary mount process is started with unix socket option.

So we need to register rpc notifications for unix sockets as
well.

Change-Id: Ie52fb97195d78e1fde43ee966174bc4274f68f7e
BUG: 1296024
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/13181
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Atin Mukherjee

glusterd: Disallow peer with existing volumes to be probed in cluster

2015-12-29T09:09:03+00:00

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

As of now we do allow peer to get added in the trusted storage pool even if it
has a volume configured. This is definitely not a supported configuration and
can lead to issues as we never claim to support merging clusters. A single node
running a standalone volume can be considered as a cluster.

Change-Id: Id0cf42d6e5f20d6bfdb7ee19d860eee67c7c45be
BUG: 1288963
Signed-off-by: Atin Mukherjee 
Reviewed-on: http://review.gluster.org/12864
Tested-by: NetBSD Build System 
Reviewed-by: Kaushal M 
Tested-by: Gluster Build System 
Reviewed-on: http://review.gluster.org/12888