glusterfs.git, branch v6.0

doc: Final version of release-6 release notes

2019-03-19T14:17:57+00:00

Fixes: bz#1672818
Change-Id: I6a98985a7f25bc2b85af5bd85f4be3ffac7d619d
Signed-off-by: ShyamsundarR

release-notes/6.0: Add ctime feature changes in release notes

2019-03-19T13:51:05+00:00

Change-Id: I3a305b9eb292a450c83de5628ceeadcb0a44afc7
updates: bz#1672818
Signed-off-by: Kotresh HR 
Signed-off-by: ShyamsundarR

release-notes: add status of gd2 and a highlights section

2019-03-19T13:51:05+00:00

Change-Id: Idd4fd07b3fcdd7810c242eff0dcca9072048a43e
fixes: bz#1672818
Signed-off-by: Amar Tumballi 
Signed-off-by: ShyamsundarR

glusterfsd: Brick is getting crash at the time of startup

2019-03-13T11:18:23+00:00

Problem: Brick is getting crash because graph was not activated
         at the time of accessing server_conf

Solution: To avoid the crash check ctx->active before processing
          a request

> Change-Id: Ib112e0eace19189e45f430abdac5511c026bed47
> fixes: bz#1687705
>(cherry picked from commit 67f48bfcc16a38052e6c9ae7c25e69b03b8ae008)
> (Reviewed on upstream link https://review.gluster.org/#/c/glusterfs/+/22339/)

Change-Id: I1367c564f04edbad145575b811c67522cc318851
fixes: bz#1688218
Signed-off-by: Mohit Agrawal

rpm: add thin-arbiter package

2019-03-13T01:48:26+00:00

Discussion on thin arbiter volume -
https://github.com/gluster/glusterfs/issues/352#issuecomment-350981148

Main idea of having this rpm package is to deploy thin-arbiter
without glusterd and other commands on a node, and all we need
on that tie-breaker node is to run a single glusterfs command.
Also note that, no other glusterfs installation needs
thin-arbiter.so.

Make sure RPM contains sample vol file, which can work by default,
and a script to configure that volfile, along with translator image.

Change-Id: Ibace758373d8a991b6a19b2ecc60c93b2f8fc489
updates: bz#1672818
Signed-off-by: Amar Tumballi 
Signed-off-by: Ashish Pandey 
(cherry picked from commit ca9bef7f1538beb570fcb190ff94f86f0b8ba38a)

doc: Update release notes for Samba integration

2019-03-12T20:56:57+00:00

Change-Id: I2a246111522bd3cb0c9b228ed3387e72b0ac20a4
updates: bz#1672818
Signed-off-by: Anoop C S

eventsapi: Fix error while handling GlusterCmdException

2019-03-12T20:53:37+00:00

`GlusterCmdException` was wrongly accessed instead of accessing
`GlusterCmdException.message`.

Fixes: bz#1687248
Change-Id: I35ec1b05726050bfd8761e05ad9b9e47917dc0c6
Signed-off-by: Aravinda VK 
(cherry picked from commit 27f6375df009c8c4798b72aeafce79456007d21f)

glusterfsd: Multiple shd processes are spawned on brick_mux environment

2019-03-12T20:52:59+00:00

Problem: Multiple shd processes are spawned while starting volumes
         in the loop on brick_mux environment.glusterd spawn a process
         based on a pidfile and shd daemon is taking some time to
         update pid in pidfile due to that glusterd is not able to
         get shd pid

Solution: Commit cd249f4cb783f8d79e79468c455732669e835a4f changed
          the code to update pidfile in parent for any gluster daemon
          after getting the status of forking child in parent.To resolve
          the same correct the condition update pidfile in parent only
          for glusterd and for rest of the daemon pidfile is updated in
          child

> Change-Id: Ifd14797fa949562594a285ec82d58384ad717e81
> fixes: bz#1684404
> (Cherry pick from commit 66986594a9023c49e61b32769b7e6b260b600626)
> (Reviewed on upstream link https://review.gluster.org/#/c/glusterfs/+/22290/)

Change-Id: I9a68064d2da1acd0ec54b4071a9995ece0c3320c
fixes: bz#1683880
Signed-off-by: Mohit Agrawal

cluster/afr: Send truncate on arbiter brick from SHD

2019-03-12T20:51:47+00:00

Problem:
In an arbiter volume configuration SHD will not send any writes onto the arbiter
brick even if there is data pending marker for the arbiter brick. If we have a
arbiter setup on the geo-rep master and there are data pending markers for the files
on arbiter brick, SHD will not mark any data changelog during healing. While syncing
the data from master to slave, if the arbiter-brick is considered as ACTIVE, then
there is a chance that slave will miss out some data. If the arbiter brick is being
newly added or replaced there is a chance of slave missing all the data during sync.

Fix:
If there is data pending marker for the arbiter brick, send truncate on the arbiter
brick during heal, so that it will record truncate as the data transaction in changelog.

Change-Id: I3242ba6cea6da495c418ef860d9c3359c5459dec
fixes: bz#1687672
Signed-off-by: karthik-us

glusterd: glusterd memory leak while running "gluster v profile" in a loop

2019-03-12T20:51:03+00:00

Problem: glusterd has memory leak while running "gluster v profile"
         in a loop

Solution: Resolve leak code path to avoid leak

> Change-Id: Id608703ff6d0ad34ed8f921a5d25544e24cfadcd
> fixes: bz#1685414
> (Cherry pick from commit 9374484917466dff4688d96ff7faa0de1c804a6c)
> (Reviewed on link https://review.gluster.org/#/c/glusterfs/+/22301/)

Change-Id: I1ca118265f97b188f94b3d5cff649ec36cb18ca0
fixes: bz#1685771
Signed-off-by: Mohit Agrawal