glusterfs.git/extras/hook-scripts, branch v3.9.1

ganesha/scripts : find export id for already exported volume in S31ganesha-start.sh

2016-12-19T10:06:06+00:00

Upstream reference :
>Change-Id: Iada90ed215966d3f526fa20aa5359b67f25a6944
>BUG: 1401822
>Signed-off-by: Jiffin Tony Thottan 
>Reviewed-on: http://review.gluster.org/16037
>Smoke: Gluster Build System 
>NetBSD-regression: NetBSD Build System 
>CentOS-regression: Gluster Build System 
>Reviewed-by: soumya k 
>Reviewed-by: Kaleb KEITHLEY 
>(cherry picked from commit 58a58e706da73ee751b7cd98c23e6675667fefdb)

Change-Id: Iada90ed215966d3f526fa20aa5359b67f25a6944
BUG: 1403144
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: http://review.gluster.org/16093
CentOS-regression: Gluster Build System 
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Kaleb KEITHLEY

glusterd/ganesha : handle volume reset properly for ganesha options

2016-12-08T03:07:40+00:00

The "gluster volume reset" should first unexport the volume and then delete
export configuration file. Also reset option is not applicable for ganesha.enable
if volume value is "all".
This patch also changes the name of create_export_config into manange_export_config

Upstream reference :
>Change-Id: Ie81a49e7d3e39a88bca9fbae5002bfda5cab34af
>BUG: 1397795
>Signed-off-by: Jiffin Tony Thottan 
>Reviewed-on: http://review.gluster.org/15914
>Smoke: Gluster Build System 
>NetBSD-regression: NetBSD Build System 
>CentOS-regression: Gluster Build System 
>Reviewed-by: soumya k 
>Reviewed-by: Kaleb KEITHLEY 
>Signed-off-by: Jiffin Tony Thottan 

Change-Id: Ie81a49e7d3e39a88bca9fbae5002bfda5cab34af
BUG: 1402366
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: http://review.gluster.org/16054
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY

ganesha/scripts : avoid incrementing Export Id value for already exported volumes

2016-12-05T07:01:01+00:00

Currently a volume will unexport when it stops and reexport it during volume start
using hook script. And also it increments the value for export id for each reexport.
Since a hook script is called from every node parallely which may led inconsistency
for export id value.
Upstream reference :
>Change-Id: Ib9f19a3172b2ade29a3b4edc908b3267c68c0b20
>BUG: 1399186
>Signed-off-by: Jiffin Tony Thottan 
>Reviewed-on: http://review.gluster.org/15948
>Smoke: Gluster Build System 
>NetBSD-regression: NetBSD Build System 
>CentOS-regression: Gluster Build System 
>Reviewed-by: soumya k 
>Reviewed-by: Kaleb KEITHLEY 
>(cherry picked from commit 76eef16d762f500df500de0d3187aff23dc39ac6)

Change-Id: Ib9f19a3172b2ade29a3b4edc908b3267c68c0b20
BUG: 1401011
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: http://review.gluster.org/16013
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY 
NetBSD-regression: NetBSD Build System

ganesha/scripts : use export id for dbus signals

2016-11-18T11:37:58+00:00

Currently for add export and update export parameter passed for executing those signal
is "PATH". This is based on assumption that volume name and PATH will always be same.
But it is wrong for subdir exports. The only reliable parameter in export configuration
file is "Export_Id".

Backport details
> Change-Id: Ic63ff44ac7736e14502034b74beaae27292eddf9
> BUG: 1389746
> Signed-off-by: Jiffin Tony Thottan 
> Reviewed-on: http://review.gluster.org/15751
> Smoke: Gluster Build System 
> NetBSD-regression: NetBSD Build System 
> CentOS-regression: Gluster Build System 
> Reviewed-by: soumya k 
> Reviewed-by: Kaleb KEITHLEY 
> Signed-off-by: Jiffin Tony Thottan 

Change-Id: Ic63ff44ac7736e14502034b74beaae27292eddf9
BUG: 1396332
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: http://review.gluster.org/15875
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Kaleb KEITHLEY 
CentOS-regression: Gluster Build System

ganesha/scripts : modify start hook script for shared storage changes

2016-10-11T12:18:34+00:00

Upstream reference:
>Change-Id: Ib8dfe41d06ae0756af8f1c110fc774ac16bdc581
>BUG: 1377607
>Signed-off-by: Jiffin Tony Thottan 
>Reviewed-on: http://review.gluster.org/15535
>Smoke: Gluster Build System 
>NetBSD-regression: NetBSD Build System 
>Reviewed-by: Kaleb KEITHLEY 
>CentOS-regression: Gluster Build System 
>Reviewed-by: soumya k 
>Reviewed-by: Niels de Vos 
>(cherry picked from commit 7407266684334203c21e260bb0b3527ca94bb507)

Change-Id: Ib8dfe41d06ae0756af8f1c110fc774ac16bdc581
BUG: 1379996
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: http://review.gluster.org/15586
NetBSD-regression: NetBSD Build System 
Reviewed-by: Niels de Vos 
CentOS-regression: Gluster Build System 
Smoke: Gluster Build System

core: assorted typos and spelling mistakes reported by Debian lintian

2016-05-18T09:21:42+00:00

Also missing bang (!) in #!/bin/bash in shell scripts.

Change-Id: I567a4be8f0f31f6285550f243fe802895f6bc43b
BUG: 1336793
Reported-by: Patrick Matthäi 
Signed-off-by: Kaleb S KEITHLEY 
Reviewed-on: http://review.gluster.org/14398
NetBSD-regression: NetBSD Build System 
Reviewed-by: Niels de Vos 
Smoke: Gluster Build System 
Reviewed-by: Kotresh HR 
CentOS-regression: Gluster Build System

Revert "NFS-Ganesha : scripts related changes for supporting multiple export entires for volume"

2016-04-24T14:29:47+00:00

This reverts change-id I2286af4877f96f4334435818f67beea87efa2b1f.
While testing, I had found that ganesha-ha.sh is not working as expected. It is
almost equivalent to rewrite entire thing again

Change-Id: Ia85e50fe8e043e8a2bc6441b7c45dcc726b36672
BUG: 1275966
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: http://review.gluster.org/13673
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Soumya Koduri 
Reviewed-by: Kaleb S KEITHLEY 
Reviewed-by: Niels de Vos 
Smoke: Gluster Build System

NFS-Ganesha : scripts related changes for supporting multiple export entires for volume

2016-03-01T08:00:04+00:00

Previously script such as dbus-send.sh, ganesha-ha.sh can handle only one EXPORT{} block.

Change-Id: I2286af4877f96f4334435818f67beea87efa2b1f
BUG: 1275966
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: http://review.gluster.org/13283
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Kaleb KEITHLEY 
Reviewed-by: Jeff Darcy

quota: heal object-limit on a root dir of a newly added brick

2016-02-28T05:30:40+00:00

When a new brick is added, xattr trusted.glusterfs.quota.limit-objects
is not healed on a root directory.
This patch will fix the problem

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

quota: fix quota hook script for add-brick

2016-02-09T03:58:56+00:00

Hook script should not call any CLI commands
as this can cause parallel operation problem,
so remove quota list command from the script

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