glusterfs.git, branch v7.8

doc: Added release 7.8 notes

2020-09-28T06:21:31+00:00

Fixes: #1517

Change-Id: I9bbd28ef3614fdcbce11e798a38149a5e00b75c0
Signed-off-by: Rinku Kothiya

build: when building with tirpc, link xlators, etc., with libtirpc

2020-09-27T09:17:56+00:00

uncovered on Ubuntu Groovy (20.10, ubuntu's bleeding edge devel dist),
seems to now have stricter link semantics than it did when we last
built 8.1 and 7.5.

Many xlators actually do have direct calls to xdr_sizeof(), so strictly
speaking they should be linked with libtirpc.

Change-Id: Iee1fd3528fde19db397c4eae6978d9b9a2c3e17f
Updates: #1002
Signed-off-by: Kaleb S. KEITHLEY

glusterd: readdir-ahead off by default

2020-09-27T09:15:29+00:00

Changing the default value of readdir-ahead to
off, but it can be enabled/disabled later on if with
gluster vol set  performance.readdir-ahead enabel/disable
command.

Updates: #1472

Change-Id: Idb3e16e8be98d7a811fc8e5d09906919ef50fbab
Signed-off-by: nik-redhat 
(cherry picked from commit 84a4cf76219b6187fc625740d1a1ebbe40e9f22c)

open-behind: implement create fop

2020-09-27T09:13:12+00:00

Open behind didn't implement create fop. This caused that files created
were not accounted for the number of open fd's. This could cause future
opens to be delayed when they shouldn't.

This patch implements the create fop. It also fixes a problem when
destroying the stack: when frame->local was not NULL, STACK_DESTROY()
tried to mem_put() it, which is not correct.

Fixes: #1440
Change-Id: Ic982bad07d4af30b915d7eb1fbcef7a847a45869
Signed-off-by: Xavi Hernandez

geo-rep: Fix string comparison

2020-09-09T10:19:10+00:00

Backport of:
  >Patch link: https://review.gluster.org/#/c/glusterfs/+/24865/
  >Fixes: #1438
  >Change-Id: If9f1c2e89e504512bcf77608fb4a4fedb19f0399
  >Signed-off-by: Kotresh HR 

Fixes: #1438
Change-Id: If9f1c2e89e504512bcf77608fb4a4fedb19f0399
Signed-off-by: Shwetha K Acharya 
(cherry picked from commit 005d2ac1d8cc57e0e36f7cf230ae09a4f860bd16)

libglusterfs: fix dict leak

2020-09-07T13:15:18+00:00

Problem:
gf_rev_dns_lookup_cached() allocated struct dnscache->dict if it was null
but the freeing was left to the caller.

Fix:
Moved dict allocation and freeing into corresponding init and fini
routines so that its easier for the caller to avoid such leaks.

Updates: #1000
Change-Id: I90d6a6f85ca2dd4fe0ab461177aaa9ac9c1fbcf9
Signed-off-by: Ravishankar N 
(cherry picked from commit 079f7a7d8a2bd85070c1da4dde2452ca82a1cdbb)

glusterd: cksum mismatch on upgrading to latest gluster

2020-09-04T13:50:44+00:00

Issue:
In gluster versions less than 7, the checksums were calculated
whether or not the quota is enabled or not, and that cksum value
was also getting stored in the quota.cksum file. But, from gluster
7 version onwards cksum was calculated only if the quota is enabled.
Due to this, the cksums in quota.cksum files differ after upgrading.

Fix:
Added a check to see if the OP_VERSION is less than 7 then, follow
the previous method otherwise, move as per the latest changes for
cksum calculation.

This changes for the cksum calculation was done in
this commit : https://github.com/gluster/glusterfs/commit/3b5eb592f5

Updates: #1332

Change-Id: I7a95e5e5f4d4be4983fb7816225bf9187856c003
Signed-off-by: nik-redhat 
(cherry picked from commit 865cca1190e233381f975ff36118f46e29477dcf)
Signed-off-by: nik-redhat

afr: add null check for thin-arbiter gfid.

2020-08-27T20:28:19+00:00

Problem:
Lookup/creation of thin-arbiter ID file happens in background during
mounting. On new volumes, if the  ID file creation is in progress, and a
FOP fails on data brick, a post-op (xattrop) is attemtped on TA. Since
the TA file's gfid is null at this point, the ASSERT checks in protocol/
client causes a crash.

Fix:
Given that we decided to do Lookup/creation of thin-arbiter in
background, fail the other AFR FOPS on TA if the ID file's gfid is null
instead of winding it down to protocol/client.

Also remove afr_changelog_thin_arbiter_post_op() which seems to be dead
code.

Updates: #763
Change-Id: I70dc666faf55cc5c8f7cf8e7d36085e4fa399c4d
Signed-off-by: Ravishankar N 
(cherry picked from commit f9b5074394e3d2f3b6728aab97230ba620879426)

cluster/afr: Delay post-op for fsync

2020-08-27T20:24:44+00:00

Problem:
AFR doesn't delay post-op for fsync fop. For fsync heavy workloads
this leads to un-necessary fxattrop/finodelk for every fsync leading
to bad performance.

Fix:
Have delayed post-op for fsync. Add special flag in xdata to indicate
that afr shouldn't delay post-op in cases where either the
process will terminate or graph-switch would happen. Otherwise it leads
to un-necessary heals when the graph-switch/process-termination
happens before delayed-post-op completes.

Fixes: #1253
Change-Id: I531940d13269a111c49e0510d49514dc169f4577
Signed-off-by: Pranith Kumar K

open-behind: fix call_frame leak

2020-08-20T14:43:02+00:00

When an open was delayed, a copy of the frame was created because the
current frame was used to unwind the "fake" open. When the open was
actually sent, the frame was correctly destroyed. However if the file
was closed before needing to send the open, the frame was not destroyed.

This patch correctly destroys the frame in all cases.

Change-Id: I8c00fc7f15545c240e8151305d9e4cf06d653926
Signed-off-by: Xavi Hernandez 
Fixes: #1440