Change in ...nfs-ganesha[next]: [GPFS] Don't fail getattrs() if getting fs_locations fails
by Madhu Thorat (GerritHub)
Madhu Thorat has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/450725
Change subject: [GPFS] Don't fail getattrs() if getting fs_locations fails
......................................................................
[GPFS] Don't fail getattrs() if getting fs_locations fails
Currently in FSAL_GPFS we fail getattrs() if fs_locations
attribute is requested by the client, but getting
fs_locations attribute fails.
Failure of fs_locations is not unusual, so don't fail
GPFS getattrs() if getting fs_locations attribute fails.
Change-Id: I34c7c294574e025de200387464232711ec5392ef
Signed-off-by: Madhu Thorat <madhu.punjabi(a)in.ibm.com>
---
M src/FSAL/FSAL_GPFS/fsal_attrs.c
M src/FSAL/FSAL_GPFS/handle.c
2 files changed, 15 insertions(+), 5 deletions(-)
git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/25/450725/1
--
To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/450725
To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings
Gerrit-Project: ffilz/nfs-ganesha
Gerrit-Branch: next
Gerrit-Change-Id: I34c7c294574e025de200387464232711ec5392ef
Gerrit-Change-Number: 450725
Gerrit-PatchSet: 1
Gerrit-Owner: Madhu Thorat <madhu.punjabi(a)in.ibm.com>
Gerrit-MessageType: newchange
5 years
Announce Push of V2.8-dev.24
by Frank Filz
Branch next
Tag:V2.8-dev.24
NOTE: This merge includes and ntirpc pullup - please update your submodule
Release Highlights
* Pull up NSM fix from ntirpc
* Misc openflags fixes
* Fix syntax error in ganesha_stats script
* Misc dupreq fixes
* Invalidate parent handle of a directory for invalidate UP call
* Call _9p_worker_shutdown when CORE_OPTION_9P is set
* rpc_callback: don't issue CB_NULL on new v4.1 channels
* GTest - fix for DSO changes
Signed-off-by: Frank S. Filz <ffilzlnx(a)mindspring.com>
Contents:
a9d6237 Frank S. Filz V2.8-dev.24
c84baf9 Daniel Gryniewicz Pull up NSM fix from ntirpc
c7f1f83 Daniel Gryniewicz GTest - fix for DSO changes
6b066ce Jeff Layton rpc_callback: don't issue CB_NULL on new v4.1 channels
9adcb12 Madhu Thorat Call _9p_worker_shutdown when CORE_OPTION_9P is set
788e2ae Madhu Thorat Invalidate parent handle of a directory for invalidate
UP call
7068cd8 Malahal Naineni Remove drc field from dupreq and avoid memory leak
d7b9734 Malahal Naineni Release dupreq's ref on drc just before freeing the
dupreq.
fd3c42b Malahal Naineni Handle dupreq hash deletion race
ce7f5be Malahal Naineni Fix syntax error in ganesha_stats script
b0da1bc Sachin Punadikar Do not store transient open flags with fd
89c6c4a Malahal Naineni Remove unused openflags
5 years
Question about recovery in cluster envirnment
by fanzi2009＠hotmail.com
Hi ,
Suppose I have mulitple nfs-ganesha servers behind a load balancer. All nfs clients connect the load balancer, then balancer choose a nfs-ganesha server and redirect the request to it. When a nfs-ganesha (Ganesha-A)which has connection with a client restart in a time, the server enter grace period and read previous clients from backend. However, as client connection is broken and load balancer choose another nfs-ganesha sever(Ganesha-B). Even the client want to reclaim open and clock, Ganesha-B is not in grace period. In this scenario, how could client relaim the resource?
Thanks,
Marvin
5 years
Ganesha 2.7.3 / ntirpc 1.7.3
by Daniel Gryniewicz
Today, I've released ntirpc 1.7.3 and Ganesha 2.7.3.
The ntirpc release has only one fix, but it's important for NFSv3
locking on may systems. The Ganesha release has some fixes for readdir,
a number of fixes to FSALs, mostly CEPH and GLUSTER, and considerable
fixes to the RADOS grace backend.
This is a stable point release.
Daniel
5 years
Change in ...nfs-ganesha[next]: Call _9p_worker_shutdown when CORE_OPTION_9P is set
by Madhu Thorat (GerritHub)
Madhu Thorat has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/450240
Change subject: Call _9p_worker_shutdown when CORE_OPTION_9P is set
......................................................................
Call _9p_worker_shutdown when CORE_OPTION_9P is set
_9p_worker_init() is called when CORE_OPTION_9P is set.
But _9p_worker_shutdown() is called without checking if
CORE_OPTION_9P is set, which leads to crash during shutdown
if CORE_OPTION_9P is not set.
To fix this call _9p_worker_shutdown() when CORE_OPTION_9P
is set.
Change-Id: Ibe848ba060fbbdee562c011c2af1efa32625eabe
Signed-off-by: Madhu Thorat <madhu.punjabi(a)in.ibm.com>
---
M src/MainNFSD/nfs_admin_thread.c
1 file changed, 10 insertions(+), 8 deletions(-)
git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/40/450240/1
--
To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/450240
To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings
Gerrit-Project: ffilz/nfs-ganesha
Gerrit-Branch: next
Gerrit-Change-Id: Ibe848ba060fbbdee562c011c2af1efa32625eabe
Gerrit-Change-Number: 450240
Gerrit-PatchSet: 1
Gerrit-Owner: Madhu Thorat <madhu.punjabi(a)in.ibm.com>
Gerrit-MessageType: newchange
5 years
Change in ...nfs-ganesha[next]: [WIP] Remove drc field from dupreq and avoid memory leak
by Malahal (GerritHub)
Malahal has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/450129
Change subject: [WIP] Remove drc field from dupreq and avoid memory leak
......................................................................
[WIP] Remove drc field from dupreq and avoid memory leak
Currently dupreq releases a hold on drc on behalf of a req, and it has
access to drc. Since dupreqs will live beyond xprts and these holds
make the drc active not go into recycle queue ever. These dupreqs and
drcs live forever contributing to memory leaks.
It is the request that places a hold on dupreq and drc while calling
nfs_dupreq_start(). The request now releases hold on dupreq and drc
while calling nfs_dupre_rele(). With this, drc refcount will go to zero
when xprt releases drc hold.
Free any dupreqs that are in the drc hash table before freeing the drc
itsef.
Change-Id: I0b8d7798a4bd13d697216a371a90685f58d67820
Signed-off-by: Malahal Naineni <malahal(a)us.ibm.com>
---
M src/RPCAL/nfs_dupreq.c
M src/include/nfs_dupreq.h
2 files changed, 51 insertions(+), 12 deletions(-)
git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/29/450129/1
--
To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/450129
To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings
Gerrit-Project: ffilz/nfs-ganesha
Gerrit-Branch: next
Gerrit-Change-Id: I0b8d7798a4bd13d697216a371a90685f58d67820
Gerrit-Change-Number: 450129
Gerrit-PatchSet: 1
Gerrit-Owner: Malahal <malahal(a)gmail.com>
Gerrit-MessageType: newchange
5 years
Change in ...nfs-ganesha[next]: Release dupreq's ref on drc just before freeing the dupreq.
by Malahal (GerritHub)
Malahal has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/450054
Change subject: Release dupreq's ref on drc just before freeing the dupreq.
......................................................................
Release dupreq's ref on drc just before freeing the dupreq.
Currently it is released when the dupreq is taken out of the hash table,
but we may access drc from dupreq when it is not in the hash table.
A request gets a ref on drc as well as dupreq. At the end of processing
the request, we release the ref on dupreq and let the dupreq release the
ref on drc as dupreq has access to drc. So it makes sense to release the
ref on drc when we are about to free the dupreq.
Change-Id: I205201b7b8b8bd9d862545d0915178d5015b21ea
Signed-off-by: Malahal Naineni <malahal(a)us.ibm.com>
---
M src/RPCAL/nfs_dupreq.c
1 file changed, 7 insertions(+), 7 deletions(-)
git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/54/450054/1
--
To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/450054
To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings
Gerrit-Project: ffilz/nfs-ganesha
Gerrit-Branch: next
Gerrit-Change-Id: I205201b7b8b8bd9d862545d0915178d5015b21ea
Gerrit-Change-Number: 450054
Gerrit-PatchSet: 1
Gerrit-Owner: Malahal <malahal(a)gmail.com>
Gerrit-MessageType: newchange
5 years
Change in ...nfs-ganesha[next]: Handle dupreq hash deletion race
by Malahal (GerritHub)
Malahal has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/450053
Change subject: Handle dupreq hash deletion race
......................................................................
Handle dupreq hash deletion race
nfs_dupreq_finish or nfs_dupreq_delete may try to delete a dupreq from
the DRC hash table/list, so check for existence in the list before we
delete the dupreq from hash table and the list.
Change-Id: I5186accf8a2538cc6a0b6184c792316cafa0eebb
Signed-off-by: Malahal Naineni <malahal(a)us.ibm.com>
---
M src/RPCAL/nfs_dupreq.c
1 file changed, 23 insertions(+), 7 deletions(-)
git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/53/450053/1
--
To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/450053
To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings
Gerrit-Project: ffilz/nfs-ganesha
Gerrit-Branch: next
Gerrit-Change-Id: I5186accf8a2538cc6a0b6184c792316cafa0eebb
Gerrit-Change-Number: 450053
Gerrit-PatchSet: 1
Gerrit-Owner: Malahal <malahal(a)gmail.com>
Gerrit-MessageType: newchange
5 years
Change in ...nfs-ganesha[next]: GTest - fix for DSO changes
by Daniel Gryniewicz (GerritHub)
Daniel Gryniewicz has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/449905
Change subject: GTest - fix for DSO changes
......................................................................
GTest - fix for DSO changes
Change-Id: I306869a265b18668fe9a55e3816807bc6f61109f
Signed-off-by: Daniel Gryniewicz <dang(a)redhat.com>
---
M src/gtest/CMakeLists.txt
M src/gtest/fsal_api/CMakeLists.txt
M src/gtest/nfs4/CMakeLists.txt
3 files changed, 58 insertions(+), 48 deletions(-)
git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/05/449905/1
--
To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/449905
To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings
Gerrit-Project: ffilz/nfs-ganesha
Gerrit-Branch: next
Gerrit-Change-Id: I306869a265b18668fe9a55e3816807bc6f61109f
Gerrit-Change-Number: 449905
Gerrit-PatchSet: 1
Gerrit-Owner: Daniel Gryniewicz <dang(a)redhat.com>
Gerrit-MessageType: newchange
5 years
