glusterfs.git, branch v5.11 doc: Added release 5.11 notes 2019-12-09T09:46:37+00:00 Hari Gowtham hgowtham@redhat.com 2019-12-09T05:34:06+00:00 7c0ef8f5c0ca30c4e889ff5ba22eca490572fc75 Fixes: bz#1762175 Change-Id: Ifaf8eb242d98b96ce83e5669b5fb08a18b7dee6a Signed-off-by: Hari Gowtham <hgowtham@redhat.com> 
Fixes: bz#1762175

Change-Id: Ifaf8eb242d98b96ce83e5669b5fb08a18b7dee6a
Signed-off-by: Hari Gowtham <hgowtham@redhat.com>
inode: fix wrong loop count in __inode_ctx_free 2019-12-06T10:32:29+00:00 Xie Changlong xiechanglong@cmss.chinamobile.com 2019-05-17T10:33:11+00:00 4ccea5328016aaa420b0ffc43d2a2fbe9f7c8973 Avoid serious memory leak fixes: bz#1779284 Change-Id: Ic61a8fdd0e941e136c98376a87b5a77fa8c22316 Signed-off-by: Xie Changlong <xiechanglong@cmss.chinamobile.com> (cherry picked from commit 93156e203c2f51d8a4047889a4c769564b8107b1) 
Avoid serious memory leak

fixes: bz#1779284
Change-Id: Ic61a8fdd0e941e136c98376a87b5a77fa8c22316
Signed-off-by: Xie Changlong <xiechanglong@cmss.chinamobile.com>
(cherry picked from commit 93156e203c2f51d8a4047889a4c769564b8107b1)
system/posix-acl: update ctx only if iatt is non-NULL 2019-12-06T10:31:19+00:00 Homma homma@allworks.co.jp 2019-07-05T10:40:41+00:00 f0f042780e5e8796a6a8e8fd9935fdc7bd974527 We need to safe-guard against possible zero'ing out of iatt structure in acl ctx, which can cause many issues. Backport of: > fixes: bz#1668286 > Change-Id: Ie81a57d7453a6624078de3be8c0845bf4d432773 > Signed-off-by: Amar Tumballi <amarts@redhat.com> (cherry-picked from commit 6bf9637a93011298d032332ca93009ba4e377e46) fixes: bz#1767305 Change-Id: Ie81a57d7453a6624078de3be8c0845bf4d432773 Signed-off-by: Alan Orth <alan.orth@gmail.com> 
We need to safe-guard against possible zero'ing out of iatt
structure in acl ctx, which can cause many issues.

Backport of:
> fixes: bz#1668286
> Change-Id: Ie81a57d7453a6624078de3be8c0845bf4d432773
> Signed-off-by: Amar Tumballi <amarts@redhat.com>

(cherry-picked from commit 6bf9637a93011298d032332ca93009ba4e377e46)
fixes: bz#1767305
Change-Id: Ie81a57d7453a6624078de3be8c0845bf4d432773
Signed-off-by: Alan Orth <alan.orth@gmail.com>
Detach iot_worker to release its resources 2019-11-05T08:25:48+00:00 Liguang Li liguang.lee6@gmail.com 2019-11-05T08:25:39+00:00 aa60bea1753bb744c892b669a3e693803b0db385 When iot_worker terminates, its resources have not been reaped, which will consumes lots of memory. Detach iot_worker to automically release its resources back to the system. Change-Id: I71fabb2940e76ad54dc56b4c41aeeead2644b8bb fixes: bz#1718734 Signed-off-by: Liguang Li <liguang.lee6@gmail.com> Signed-off-by: N Balachandran <nbalacha@redhat.com> 
When iot_worker terminates, its resources have not been reaped, which
will consumes lots of memory.

Detach iot_worker to automically release its resources back to the
system.

Change-Id: I71fabb2940e76ad54dc56b4c41aeeead2644b8bb
fixes: bz#1718734
Signed-off-by: Liguang Li <liguang.lee6@gmail.com>
Signed-off-by: N Balachandran <nbalacha@redhat.com>
cluster/afr: Heal entries when there is a source & no healed_sinks 2019-10-11T07:19:03+00:00 karthik-us ksubrahm@redhat.com 2019-09-05T10:44:50+00:00 11cbd2da4a065332d0b8eee624b654a9991a0170 Problem: In a situation where B1 blames B2, B2 blames B1 and B3 doesn't blame anything for entry heal, heal will not complete even though we have clear source and sinks. This will happen because while doing afr_selfheal_find_direction() only the bricks which are blamed by non-accused bricks are considered as sinks. Later in __afr_selfheal_entry_finalize_source() when it tries to mark all the non-sources as sinks it fails to do so because there won't be any healed_sinks marked, no witness present and there will be a source. Fix: If there is a source and no healed_sinks, then reset all the locked sources to 0 and healed sinks to 1 to do conservative merge. Change-Id: If40d8bc95d52a52b2730f55bdcf135109b421548 Fixes: bz#1760710 Signed-off-by: karthik-us <ksubrahm@redhat.com> 
Problem:
In a situation where B1 blames B2, B2 blames B1 and B3 doesn't blame
anything for entry heal, heal will not complete even though we have
clear source and sinks. This will happen because while doing
afr_selfheal_find_direction() only the bricks which are blamed by
non-accused bricks are considered as sinks. Later in
__afr_selfheal_entry_finalize_source() when it tries to mark all the
non-sources as sinks it fails to do so because there won't be any
healed_sinks marked, no witness present and there will be a source.

Fix:
If there is a source and no healed_sinks, then reset all the locked
sources to 0 and healed sinks to 1 to do conservative merge.

Change-Id: If40d8bc95d52a52b2730f55bdcf135109b421548
Fixes: bz#1760710
Signed-off-by: karthik-us <ksubrahm@redhat.com>
doc: Added release 5.10 notes 2019-10-09T08:53:02+00:00 Hari Gowtham hgowtham@redhat.com 2019-10-09T08:51:16+00:00 3e12379fba83b8107117a6dedc99a02e31bd9bb1 Fixes: bz#1759832 Change-Id: I9c38181ec50d9b18ebc8bb8e1290f20a006be3bc Signed-off-by: Hari Gowtham <hgowtham@redhat.com> 
Fixes: bz#1759832

Change-Id: I9c38181ec50d9b18ebc8bb8e1290f20a006be3bc
Signed-off-by: Hari Gowtham <hgowtham@redhat.com>
geo-rep : fix mountbroker setup 2019-09-23T12:39:08+00:00 Sunny Kumar sunkumar@redhat.com 2019-05-13T09:02:53+00:00 fd4144de3df743af29e81f70bc7af421a1b8220d Problem: Unable to setup mountbroker root directory while creating geo-replication session for non-root user. Casue: With patch[1] which defines the max-port for glusterd one extra sapce got added in field of 'option max-port'. [1]. https://review.gluster.org/#/c/glusterfs/+/21872/ In geo-rep spliting of key-value pair form vol file was done on the basis of space so this additional space caused "ValueError: too many values to unpack". Solution: Use split so that it can treat consecutive whitespace as a single separator. Backport of: https://review.gluster.org/#/c/glusterfs/+/22716/. >Fixes: bz#1709248 >Change-Id: Ia22070a43f95d66d84cb35487f23f9ee58b68c73 >Signed-off-by: Sunny Kumar <sunkumar@redhat.com> >(cherry picked from commit 3dd03146bb7037ae2ebea0579d0b81be27fdd927) Change-Id: Ia22070a43f95d66d84cb35487f23f9ee58b68c73 Fixes: bz#1750230 Signed-off-by: Sunny Kumar <sunkumar@redhat.com> 
Problem:

Unable to setup mountbroker root directory while creating geo-replication
session for non-root user.

Casue:
With patch[1] which defines the max-port for glusterd one extra sapce
got added in field of 'option max-port'.
[1]. https://review.gluster.org/#/c/glusterfs/+/21872/

In geo-rep spliting of key-value pair form vol file was done on the
basis of space so this additional space caused "ValueError: too many values
to unpack".

Solution:
Use split so that it can treat consecutive whitespace as a single separator.

Backport of:
https://review.gluster.org/#/c/glusterfs/+/22716/.

>Fixes: bz#1709248
>Change-Id: Ia22070a43f95d66d84cb35487f23f9ee58b68c73
>Signed-off-by: Sunny Kumar <sunkumar@redhat.com>
>(cherry picked from commit 3dd03146bb7037ae2ebea0579d0b81be27fdd927)

Change-Id: Ia22070a43f95d66d84cb35487f23f9ee58b68c73
Fixes: bz#1750230
Signed-off-by: Sunny Kumar <sunkumar@redhat.com>
afr/lookup: Pass xattr_req in while doing a selfheal in lookup 2019-09-05T12:43:45+00:00 Mohammed Rafi KC rkavunga@redhat.com 2019-09-05T12:42:35+00:00 fcfcb0ad04402a34f07075d29981922a6dbc858c We were not passing xattr_req when doing a name self heal as well as a meta data heal. Because of this, some xdata was missing which causes i/o errors Backport of>https://review.gluster.org/#/c/glusterfs/+/23024/ >Change-Id: Ibfb1205a7eb0195632dc3820116ffbbb8043545f >Fixes: bz#1728770 >Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com> Change-Id: I740ccdbfcf2667fe4a850c12ecdc4b9eeed08293 Fixes: bz#1749352 Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com> 
We were not passing xattr_req when doing a name self heal
as well as a meta data heal. Because of this, some xdata
was missing which causes i/o errors

Backport of>https://review.gluster.org/#/c/glusterfs/+/23024/
>Change-Id: Ibfb1205a7eb0195632dc3820116ffbbb8043545f
>Fixes: bz#1728770
>Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

Change-Id: I740ccdbfcf2667fe4a850c12ecdc4b9eeed08293
Fixes: bz#1749352
Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
protocol/client: propagte GF_EVENT_CHILD_PING only for connections to brick 2019-08-09T05:03:46+00:00 Raghavendra G rgowdapp@redhat.com 2019-06-04T13:52:45+00:00 23e391b6d1db72563a0f8e239d7877c9839d49fd Two reasons: * ping responses from glusterd may not be relevant for Halo replication. Instead, it might be interested in only knowing whether the brick itself is responsive. * When a brick is killed, propagating GF_EVENT_CHILD_PING of ping response from glusterd results in GF_EVENT_DISCONNECT spuriously propagated to parent xlators. These DISCONNECT events are from the connections client establishes with glusterd as part of its reconnect logic. Without GF_EVENT_CHILD_PING, the last event propagated to parent xlators would be the first DISCONNECT event from brick and hence subsequent DISCONNECTS to glusterd are not propagated as protocol/client prevents same event being propagated to parent xlators consecutively. propagating GF_EVENT_CHILD_PING for ping responses from glusterd would change the last_sent_event to GF_EVENT_CHILD_PING and hence protocol/client cannot prevent subsequent DISCONNECT events Signed-off-by: Raghavendra G <rgowdapp@redhat.com> Fixes: bz#1739336 Change-Id: I50276680c52f05ca9e12149a3094923622d6eaef (cherry picked from commit 5d66eafec581fb3209af74595784be8854ca40a4) 
Two reasons:
* ping responses from glusterd may not be relevant for Halo
  replication. Instead, it might be interested in only knowing whether
  the brick itself is responsive.
* When a brick is killed, propagating GF_EVENT_CHILD_PING of ping
  response from glusterd results in GF_EVENT_DISCONNECT spuriously
  propagated to parent xlators. These DISCONNECT events are from the
  connections client establishes with glusterd as part of its
  reconnect logic. Without GF_EVENT_CHILD_PING, the last event
  propagated to parent xlators would be the first DISCONNECT event
  from brick and hence subsequent DISCONNECTS to glusterd are not
  propagated as protocol/client prevents same event being propagated
  to parent xlators consecutively. propagating GF_EVENT_CHILD_PING for
  ping responses from glusterd would change the last_sent_event to
  GF_EVENT_CHILD_PING and hence protocol/client cannot prevent
  subsequent DISCONNECT events

Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
Fixes: bz#1739336
Change-Id: I50276680c52f05ca9e12149a3094923622d6eaef
(cherry picked from commit 5d66eafec581fb3209af74595784be8854ca40a4)
doc: Added release 5.9 notes 2019-08-06T11:27:16+00:00 hari gowtham hgowtham@redhat.com 2019-08-06T11:03:48+00:00 0386ca39690fe4cd9d07378b408a934d666321c2 Fixes: bz#1737313 Change-Id: Icc44f0d1b33de628ba5c1b0672ed56791d281dcf Signed-off-by: hari gowtham <hgowtham@redhat.com> 
Fixes: bz#1737313

Change-Id: Icc44f0d1b33de628ba5c1b0672ed56791d281dcf
Signed-off-by: hari gowtham <hgowtham@redhat.com>