glusterfs.git/xlators/mgmt/glusterd/src, branch v3.7.0beta1

quota: display error when inode-quota cmds executed with cluster ver < 3.7

2015-04-28T17:28:39+00:00

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

> In a heterogeneous cluster with op_version less than 3.7, inode quotas will
> be accounted on those bricks which has glusterfs version 3.7 and this is
> not available in older version.
> This will have incorrect values displayed when user queries inode count
> from CLI.
>
> This patch will display error when inode-quota commands
> are executed with cluster version less than 3.7
>
> Change-Id: Ia0e6d5635d1d8e7b2e2cfc3daa7b7f9e314a263a
> BUG: 1212253
> Signed-off-by: vmallika 
> Reviewed-on: http://review.gluster.org/10261
> Tested-by: Gluster Build System 
> Reviewed-by: Atin Mukherjee 
> Reviewed-by: Vijay Bellur 

Change-Id: I1ddd605e5b87a248aa85f0eab14c404895751083
BUG: 1215907
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/10415
Tested-by: NetBSD Build System
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd: Remove direct references to peerinfo in frame cookies

2015-04-28T12:49:05+00:00

RCU protection requires that we don't have  direct references to
protected data structures outside read-critical sections

This change was developed on the git branch at [1]. This commit is a
combination of the following commits on the development branch.
  82ebfdd Remove direct references to peerinfo in frame cookies
  dec4bec Remove incorrect and unneeded code from
          gd_syncop_mgmt_v3_unlock_cbk_fn
  7aced7b Use stack allocated uuid for frame cookie.
  38e4124 Address comments from 10192/2

[1]: https://github.com/kshlm/glusterfs/tree/urcu

Change-Id: Ic50e5fca0be72af5090f4cf318efa55d29075de9
BUG: 1205186
Signed-off-by: Kaushal M 
Reviewed-on: http://review.gluster.org/10399
Reviewed-by: Krishnan Parthasarathi 
Tested-by: Krishnan Parthasarathi

glusterd: incorrect rsp.op_ret handling in volume get in cli

2015-04-28T08:54:19+00:00

Cherry picked from commit 540fc2829bd63a2fa070c68ed105eb23145df406:
> Change-Id: Iabe99c06166578fc90121e7cfdca4a6a3f5328ae
> BUG: 1211132
> Signed-off-by: Atin Mukherjee 
> Reviewed-on: http://review.gluster.org/10229
> Reviewed-by: Niels de Vos 
> Tested-by: Gluster Build System 
> Reviewed-by: Kaushal M 

Change-Id: Iabe99c06166578fc90121e7cfdca4a6a3f5328ae
BUG: 1215547
Signed-off-by: Atin Mukherjee 
Reviewed-on: http://review.gluster.org/10398
Reviewed-by: Niels de Vos 
Tested-by: NetBSD Build System
Tested-by: Gluster Build System

glusterd: initialize snapd svc at volume restore path

2015-04-28T08:53:35+00:00

In restore path snapd svc was not initialized because of which any glusterd
instance which went down and came back may have uninitialized snapd svc. The
reason I used 'may' is because depending on the nodes in the cluster. In a
single node cluster this wouldn't be a problem since glusterd_spawn_daemon takes
care of initializing it.

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

Change-Id: I2da1e419a0506d3b2742c1cf39a3b9416eb3c305
BUG: 1215518
Signed-off-by: Atin Mukherjee 
Reviewed-on: http://review.gluster.org/10304
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System
Reviewed-by: Kaushal M 
(cherry picked from commit 18fd2fdd60839d737ab0ac64f33a444b54bdeee4)
Reviewed-on: http://review.gluster.org/10397
Reviewed-by: Krishnan Parthasarathi

tiering: skip CTR-xlator and config options when disabled

2015-04-26T14:35:34+00:00

When compiling with --disable-tiering, GlusterD should not contain any
references to the ChangeTimeRecorder xlator or any of the data tiering
options.

Cherry picked from commit a675ab96b917fc48fc3d7ca035590ebd7cf102bd:
> BUG: 1213125
> Change-Id: Idb46fb80f0ca8b66115e06841d9ec15ba14c24a0
> Signed-off-by: Niels de Vos 
> Reviewed-on: http://review.gluster.org/10296
> Reviewed-by: Dan Lambright 
> Tested-by: Gluster Build System 

BUG: 1215382
Change-Id: Idb46fb80f0ca8b66115e06841d9ec15ba14c24a0
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/10378
Tested-by: Gluster Build System 
Reviewed-by: Dan Lambright

features/trash : fixing trash dir option

2015-04-23T14:07:08+00:00

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

Previously, problem was caused due to buffer overflow of variable used
in the code. This patch fix the same.

Change-Id: I3df5e06044470022f9475d93d33447db35384da2
BUG: 1214563
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: http://review.gluster.org/10345
Tested-by: NetBSD Build System
Reviewed-by: Emmanuel Dreyfus 
Tested-by: Emmanuel Dreyfus 
Reviewed-by: Vijay Bellur

Fix case mistake for MKDIR_P in Makefiles

2015-04-23T05:31:42+00:00

Some makefiles used $(mkdir_p) instead of the corectly defined $(MKDIR_P).
The former is substituted as an empty string, leading to possible failures
depending of the user shell tolerance. NetBSD's /bin/sh seems to choke
more easily than Linux's /bin/bash, but if the later does not fail, it
does not created the intended directories anyway.

Resubmit after rebase in hope that regression test will have less
spurious failures.

Backport of: I8caed4000f3c91cb3a685453848fb854793945ed

BUG: 1212676
Change-Id: I393ffda8aa24bffce86f7b1f19b999ffa30c3562
Signed-off-by: Emmanuel Dreyfus 
Reviewed-on: http://review.gluster.org/10279
Tested-by: NetBSD Build System
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd: Store ping-timeout in glusterd conf in memory

2015-04-14T05:20:28+00:00

As of now glusterd_conf_t's ping-timeout was of no use and hence statedump was
not reflecting correct ping-timeout value configured in glusterd.vol

Change-Id: I76ba7b721264565751538c7fcdcb801a28317581
BUG: 1210627
Signed-off-by: Atin Mukherjee 
Reviewed-on: http://review.gluster.org/10191
Tested-by: Gluster Build System 
Reviewed-by: Krishnan Parthasarathi 
Tested-by: Krishnan Parthasarathi

NFS-Ganesha : Fixing HA script invocation and others

2015-04-13T10:36:58+00:00

gluster features.ganesha disable failed invariably.
And also, there were problems in unexporting
volumes dynamically.Fixed the above problems.

Change-Id: I29aa289dc8dc7b39fe0fd9d3098a02097ca8ca0c
BUG: 1207629
Signed-off-by: Meghana Madhusudhan 
Reviewed-on: http://review.gluster.org/10199
Reviewed-by: jiffin tony Thottan 
Reviewed-by: Kaleb KEITHLEY 
Tested-by: NetBSD Build System

glusterd: Restarting glusterd should not reset bitrot tunable value to default

2015-04-13T08:46:56+00:00

Previously when user restart glusterd then bitrot tunable value for option
"scrub-throttle", "scrub-frequency", "scrub" cleared. glusterd was not storing
these bitrot tunable value properly.

With this fix it will store scrub-throttle, scrub-frequency, scrub, bitrot
tunable value in /var/lib/glusterd/vols//info file and it will resume
these value when glusterd restart.

Change-Id: I58e756e14fbb8513a6f878f808ea148e7aa33cb0
BUG: 1209751
Signed-off-by: Gaurav Kumar Garg 
Reviewed-on: http://review.gluster.org/10159
Tested-by: Gluster Build System 
Reviewed-by: Atin Mukherjee 
Reviewed-by: Venky Shankar 
Tested-by: Venky Shankar