glusterfs.git/xlators/protocol/client, branch v8.2

protocol/client: fallback to anonymous fd for fsync

2020-03-10T06:53:16+00:00

Change-Id: I32f801206ce7fbd05aa693f44c2f140304f2e275
Fixes: bz#1810842

protocol/client: structure logging

2020-03-03T11:56:44+00:00

convert gf_msg() to gf_smsg()

Updates: #657

Change-Id: I76a09cfd283bb4ec5c4358536da66547aaf0de31
Signed-off-by: yatip

dht: Fix stale-layout and create issue

2020-02-09T02:51:31+00:00

Problem: With lookup-optimize set to on by default, a client with
stale-layout can create a new file on a wrong subvol. This will lead to
possible duplicate files if two different clients attempt to create the
same file with two different layouts.

Solution: Send in-memory layout to be cross checked at posix before
commiting a "create". In case of a mismatch, sync the client layout with
that of the server and attempt the create fop one more time.

test: Manual, testcase(attached)

fixes: bz#1786679
Change-Id: Ife0941f105113f1c572f4363cbcee65e0dd9bd6a
Signed-off-by: Susant Palai

protocol/client-rpc-fops: structure logging

2020-02-06T05:26:44+00:00

convert all gf_msg() to gf_smsg()

Updates: #657

Change-Id: Ia9d4fb17579af6586bc13d69ec7990c6cf220aac
Signed-off-by: yatip

protocol/client: Maintain connection to brick status

2020-02-05T12:13:05+00:00

Problem:
The current version of the code depends on the non-zero-port information to
propagate ping event from brick to parent layers. But as and when connection
succeeds, port is set to zero in rpc layer.So ping event is never propagated to
parent layers. Halo doesn't work without this.

Fix:
Remember the status of connection in 'private' structure and use that to decide
to propagate ping event to parent xlator.

fixes: bz#1797934
Change-Id: Ia578ba9fb3813953d2068dbba5c982ab27cc3429
Signed-off-by: Pranith Kumar K

protocol/client: structure logging

2020-02-04T04:52:35+00:00

convert all gf_msg() to gf_smsg()

Updates: #657

Change-Id: I69b228d7c7a8bc6263f9bd33710e880678d8c017
Signed-off-by: yatip

protocol/client-handshake: structure logging

2020-02-04T04:52:35+00:00

convert gf_msg() to gf_smsg()

Updates: #657

Change-Id: Iee07228cfc3a9a9cd10e89ae9eb918681b072585
Signed-off-by: yatip

protocol/client-rpc-fops_v2: structure logging

2020-02-04T04:52:35+00:00

convert gf_msg() to gf_smsg()

Updates: #657

Change-Id: Ib45f121f583c2af09bfddb23391f73a117e63213
Signed-off-by: yatip

server: Mount fails after reboot 1/3 gluster nodes

2020-01-22T09:24:35+00:00

Problem: At the time of coming up one server node(1x3) after reboot
client is unmounted.The client is unmounted because a client
is getting AUTH_FAILED event and client call fini for the graph.The
client is getting AUTH_FAILED because brick is not attached with a
graph at that moment

Solution: To avoid the unmounting the client graph throw ENOENT error
          from server in case if brick is not attached with server at
          the time of authenticate clients.

Credits: Xavi Hernandez 
Change-Id: Ie6fbd73cbcf23a35d8db8841b3b6036e87682f5e
Fixes: bz#1793852
Signed-off-by: Mohit Agrawal

dictionary: remove the 'extra_free' parameter

2020-01-21T12:28:07+00:00

This parameter may have been used in the past, but is no longer
needed. Removing it and the few locations it was actually referenced.
This allows to remove an extra memdup as well, that was not needed
in the 1st place in server_setvolume() and unserialize_rsp_direntp()
functions.

A followup separate patch will remove extra_stdfree parmeter
from the dictionary structure.

Change-Id: Ica0ff0a330672373aaa60e808b7e76ec489a0fe3
updates: bz#1193929
Signed-off-by: Yaniv Kaul