glusterfs.git/extras, branch v3.7.10

extras:add gfid-to-dirname.sh

2016-03-25T03:56:38+00:00

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

Add a script that converts the gfid-string of a directory into absolute
path name w.r.t the brick path.

Example:gfid-to-dirname.sh /home/ravi/bricks/brick1 e9c81321-f009-41b0-a009-cd77888c217e
Location of the directory corresponding to gfid:e9c81321-f009-41b0-a009-cd77888c217e is /home/ravi/bricks/brick1/d1/d2/d3/d4/d5/d6/d7/

Change-Id: I276ddf9c4f3d11a5b1932286d848b00b5ea1895d
BUG: 1320367
Signed-off-by: Ravishankar N 
(cherry picked from commit afbdcda3f4d6ffb906976064e0fa6f6b824718c8)
Reviewed-on: http://review.gluster.org/13812
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Pranith Kumar Karampuri

extra: "enable-shared-storage" key should create shared-storage

2016-03-22T04:04:20+00:00

This patch is backport of: http://review.gluster.org/#/c/11491/

Currently while creating shared storage it accept only
"cluster.enable-shared-storage" key. It should also
accept "enable-shared-storage" key.


Change-Id: I4c68782f4b7927ec8cd725e411b0b9db17d9c48d
BUG: 1319645
Signed-off-by: Gaurav Kumar Garg 

  >> Change-Id: I4c68782f4b7927ec8cd725e411b0b9db17d9c48d
  >> BUG: 1238224
  >> Signed-off-by: Gaurav Kumar Garg 
  >> Reviewed-on: http://review.gluster.org/11491
  >> Tested-by: NetBSD Build System 
  >> Tested-by: Gluster Build System 
  >> Reviewed-by: Krishnan Parthasarathi 
  >> Reviewed-by: Avra Sengupta 
(cherry picked from commit 890e58f5d4d3db9477e36cac3d16798ffe3b0480)

Change-Id: Ic77fd67b90be3381cff33f18f49eee97972eb19a
Reviewed-on: http://review.gluster.org/13794
Tested-by: Gaurav Kumar Garg 
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Atin Mukherjee

glusterd: Bug fixes for IPv6 support

2016-03-21T17:52:50+00:00

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

Problem:
Glusterd not working using ipv6 transport. The idea is with proper glusterd.vol configuration,
1. glusterd needs to listen on default port (240007) as IPv6 TCP listner.
2. Volume creation/deletion/mounting/add-bricks/delete-bricks/peer-probe
needs to work using ipv6 addresses.
3. Bricks needs to listen on ipv6 addresses.
All the above functionality is needed to say that glusterd supports ipv6 transport and this is broken.

Fix:
When "option transport.address-family inet6" option is present in glusterd.vol
file, it is made sure that glusterd creates listeners using ipv6 sockets only and also the same information is saved
inside brick volume files used by glusterfsd brick process when they are starting.

Tests Run:
Regression tests using ./run-tests.sh
IPv4: Regression tests using ./run-tests.sh for release-3.7 branch verified by comparing with clean repo.
IPv6: (Need to add the above mentioned config and also add an entry for "hostname ::1" in /etc/hosts)
    Started failing at ./tests/basic/glusterd/arbiter-volume-probe.t and ran successfully till here

Change-Id: Idd7513aa2347ce0de2b1f68daeecce1b7a39a7af
BUG: 1310445
Signed-off-by: Nithin D 
Reviewed-on: http://review.gluster.org/13787
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Atin Mukherjee

ganesha: Include a script to generate epoch value

2016-03-21T10:51:28+00:00

In a NFS-Ganesha HA cluster setup, for NFS clients to recover state
succesfully post failover, the NFS-servers should start with a unique
epoch value.

With NFS-Ganesha 2.3, the service accepts an option "EPOCH_EXEC" which
takes path of the script, generating epoch value. This script is executed before
starting nfs-ganesha service so that the generated epoch value is used
while bringing up the service.

This patch includes the script to be used by nfs-ganesha+gluster setup.

The epoch value is computed as follows -
       - first 32-bit contains the now() time
       - rest 32-bit value contains the local glusterd node uuid

Change-Id: I876ea5a3730d7c6b40503e0fec16a4a142c54a36
BUG: 1317482
Signed-off-by: Soumya Koduri 
Reviewed-on: http://review.gluster.org/13716
Smoke: Gluster Build System 
Reviewed-by: jiffin tony Thottan 
Reviewed-by: Kaleb KEITHLEY 
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System

bash-completion: Swap order of characters in egrep bracket expression

2016-03-18T06:59:04+00:00

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

Change-Id: I5132a8ffb00d03932bc6bd801eeaf237b334e2e3
BUG: 1318750
Signed-off-by: Paul Stauffer 
Reviewed-on: http://review.gluster.org/13769
Reviewed-by: Ravishankar N 
Tested-by: Ravishankar N 
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Pranith Kumar Karampuri

geo-rep: Script to Schedule Geo-replication

2016-03-08T10:00:01+00:00

This script can be used to run Geo-replication when required. can be
scheduled using cron job to run Geo-replication.

This script does the following,
  1. Stop Geo-replication if Started
  2. Start Geo-replication
  3. Set Checkpoint
  4. Check the Status and see Checkpoint is Complete.(LOOP)
  5. If checkpoint complete, Stop Geo-replication

Usage:
    python /usr/share/glusterfs/scripts/schedule_georep.py  \
                  

For example,
    python /usr/share/glusterfs/scripts/schedule_georep.py gv1 fvm1 gv2

To schedule the Geo-replication to run once in a day using cron,
   # Run daily at 08:30pm
      30 20 * * * root python /usr/share/glusterfs/scripts/schedule_georep.py \
            --no-color gv1 fvm1 gv2 >> /var/log/glusterfs/schedule_georep.log 2>&1

BUG: 1309191
Signed-off-by: Aravinda VK 
Reviewed-on: http://review.gluster.org/13279
Change-Id: Ie1507be00afd9ff189bb1664b156328dced4076a
Reviewed-on: http://review.gluster.org/13510
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Kotresh HR

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

2016-03-04T06:15:37+00:00

This is a backport of http://review.gluster.org/13422

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 

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

nfs-ganesha: pcs cluster setup needs '--name' option

2016-03-04T02:11:14+00:00

Even on fedora machines (on f22, f23), pcs cluster setup CLI
expects '--name' to be provided. This patch addresses the same.

Change-Id: Id33c8bbdc33955dd54729b10c720f4fa646f7e8c
BUG: 1314204
Signed-off-by: Soumya Koduri 
Reviewed-on: http://review.gluster.org/13590
Smoke: Gluster Build System 
Reviewed-by: jiffin tony Thottan 
CentOS-regression: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY 
NetBSD-regression: NetBSD Build System

ganesha: Read export_id on each node while performing refresh-config

2016-02-28T20:14:35+00:00

As mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1309238#c1,
there could be cases which shall result in having different ExportIDs
for the same volume on each node forming the ganesha cluster.

Hence during refresh-config, it is necessary to read the ExportID on
each of those nodes and re-export that volume with the same ID.

Change-Id: I44058352fe977ccc649d378da3b68bbfb992fcd7
BUG: 1309238
Signed-off-by: Soumya Koduri 
Reviewed-on: http://review.gluster.org/13459
CentOS-regression: Gluster Build System 
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Kaleb KEITHLEY

common-ha: reliable grace using pacemaker notify actions

2016-02-26T11:00:38+00:00

Using *-dead_ip-1 resources to track on which nodes the ganesha.nfsd
had died was found to be unreliable.

Running `pcs status` in the ganesha_grace monitor action was seen to
time out during failover; the HA devs opined that it was, generally,
not a good idea to run `pcs status` in a monitor action in any event.
They suggested using the notify feature, where the resources on all
the nodes are notified when a clone resource agent dies.

This change adds a notify action to the ganesha_grace RA. The ganesha_mon
RA monitors its ganesha.nfsd daemon. While the daemon is running, it
creates two attributes: ganesha-active and grace-active. When the daemon
stops for any reason, the attributes are deleted. Deleting the
ganesha-active attribute triggers the failover of the virtual IP (the
IPaddr RA) to another node where ganesha.nfsd is still running. The
ganesha_grace RA monitors the grace-active attribute. When the
grace-active attibute is deleted, the ganesha_grace RA stops, and will
not restart. This triggers pacemaker to trigger the notify action in
the ganesha_grace RAs on the other nodes in the cluster; which send a
DBUS message to their ganesha.nfsd.

(N.B. grace-active is a bit of a misnomer. while the grace-active
attribute exists, everything is normal and healthy. Deleting the
attribute triggers putting the surviving ganesha.nfsds into GRACE.)

To ensure that the remaining/surviving ganesha.nfsds are put into
NFS-GRACE before the IPaddr (virtual IP) fails over there is a short
delay (sleep) between deleting the grace-active attribute and the
ganesha-active attribute. To summarize:
  1. on node 2 ganesha_mon:monitor notices that ganesha.nfsd has died
  2. on node 2 ganesha_mon:monitor deletes its grace-active attribute
  3. on node 2 ganesha_grace:monitor notices that grace-active is gone
     and returns OCF_ERR_GENERIC, a.k.a. new error. When pacemaker
     tries to (re)start ganesha_grace, its start action will return
     OCF_NOT_RUNNING, a.k.a. known error, don't attempt further
     restarts.
  4. on nodes 1, 3, etc., ganesha_grace:notify receives a post-stop
     notification indicating that node 2 is gone, and sends a DBUS
     message to its ganesha.nfsd putting it into NFS-GRACE.
  5. on node 2 ganesha_mon:monitor waits a short period, then deletes
     its ganesha-active attribute. This triggers the IPaddr (virt IP)
     failover according to constraint location rules.

ganesha_nfsd modified to run for the duration, start action is invoked
to setup the /var/lib/nfs symlink, stop action is invoked to restore it.
ganesha-ha.sh modified accordingly to create it as a clone resource.

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