September 2021 - Devel - Nfs Ganesha List Archives

Change in ...nfs-ganesha[next]: Allow EXPORT pseudo path to be changed during export update

by Frank Filz (GerritHub)

Frank Filz has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/490334 ) Change subject: Allow EXPORT pseudo path to be changed during export update ...................................................................... Allow EXPORT pseudo path to be changed during export update This also fully allows adding or removing NFSv4 support from an export since we can now handle the PseudoFS swizzing that occurs. Note that an explicit PseudoFS export may be removed or added, though you can not change it from export_id 0 because we currently don't allow changing the export_id. Note that this patch doesn't handle DBUS add or remove export though that is an option to improve. I may add them to this patch (it wouldn't be that hard) but I want to get this reviewed as is right now. There are implications to a client of changing the PseudoFS. I have tested moving an export in the PseudoFS with a client mounted. The client will be able to continue accessing the export, though it may see an ESTALE error if it navigates out of the export. The current working directory will go bad and the pwd comment will fail indicating a disconnected mount. I have also seen referencing .. from the root of the export wrapping around back to the root (I believe this is how disconnected mounts are set up). FSAL_PSEUDO lookups and create handles (PUTFH or any use of an NFSv3 handle where the inode isn't cached) which fail during an export update are instead turned into ERR_FSAL_DELAY which turns into NFS4ERR_DELAY or NFS3ERR_JUKEBOX to force the client to retry under the completed update. Change-Id: I507dc17a651936936de82303ff1291677ce136be Signed-off-by: Frank S. Filz <ffilzlnx(a)mindspring.com> --- M src/FSAL/FSAL_PSEUDO/handle.c M src/MainNFSD/libganesha_nfsd.ver M src/Protocols/NFS/nfs4_pseudo.c M src/include/export_mgr.h M src/include/nfs_proto_functions.h M src/support/export_mgr.c M src/support/exports.c 7 files changed, 560 insertions(+), 203 deletions(-) git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/34/490334/1 -- To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/490334 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: I507dc17a651936936de82303ff1291677ce136be Gerrit-Change-Number: 490334 Gerrit-PatchSet: 1 Gerrit-Owner: Frank Filz <ffilzlnx(a)mindspring.com> Gerrit-MessageType: newchange

10 months

2
2
0 / 0

Monitoring in Ganesha?

by Bjorn Leffler

Apart from the counters that you can access through dbus, is there any other monitoring built into Ganesha? I'm thinking of adding it with this higher level plan: - Exporting metrics from Ganesha to Prometheus. - Aggregate data in Prometheus. - Display monitoring consoles and graphs with Grafana. - Package up Prometheus, Grafana and the preconfigured rules/dashboards as a Docker image. - This makes it straightforward to deploy monitoring alongside a Gansha binary. My rough coding plan for the code is to: - Add a USE_MONITORING directive to the CMakeLists.txt files. - Add a build dependency to the Prometheus C client <https://github.com/digitalocean/prometheus-client-c>. - Create a src/monitoring directory for the new source files and templates. - Increment counters and timers throughout the code. - Use histograms to compute latency percentiles, heatmaps, etc. Is this a good idea? Any objections or suggestions? Thanks, Bjorn

3 years

3
6
0 / 0

FW: Virtual Bakeathon: Reminder

by Frank Filz

-----Original Message----- From: Steve Dickson [mailto:steved@redhat.com] Sent: Thursday, September 30, 2021 9:37 AM To: Linux NFS Mailing list <linux-nfs(a)vger.kernel.org> Cc: NFSv4 IETF <nfsv4(a)ietf.org> Subject: Virtual Bakeathon: Reminder Hello, Just a quick reminder the VBAT coming up next week The details are here [1]. We are again going to be using an IPv6 based VPN as the testing network. Details on how to set it up are at [2]. Any question reach out to Ben Coddington <bcodding(a)redhat.com> Here at Red Hat we have been using vm in the Digital Ocean cloud [3]... I have found them to be really easy to work with and relatively inexpensive. We will again use discord [4] to communicate. Look for the VBaT channel. The contact for that is Alice Mitchell <ajmitchell(a)redhat.com> Finally I would like to propose that every day at 2:00pm (EST) we get together on the discord voice channel 'General Chat' and talk about the topics of the day: * TLS (user vs kernel) * FS-cache (Trond's favorite subject) * QUIC (Chuck's favorite subject ;-) ) * Allowing hung mount to reboot * re-export * Session-Truncking * ??? Basically anything we wan to talk about relative to what is going on in the community... or not... :-) Ideally, as Rick suggested, reaching out to people like Google and MS.. people who might have a better insight of these networking technologies... would be good... Just let them where we will be. If I have forgotten anything... I'm sure you will let me know! :-) See you Monday! steved [1] http://www.nfsv4bat.org/Events/2021/Oct/BAT/index.html [2] https://vpn.nfsv4.dev/ [3] https://www.digitalocean.com/ [4] https://discord.com

3 years, 2 months

1
0
0 / 0

disable inode & dirents cache

by Alok Sinha

My FSAL is in the main memory. Should I disable inode and dirents caching? If so, what all I save in terms of memory and open FDs. I am not worried much about saving open FDs but I do not want memory to get occupied without much benefit. How do I disable inode and dirents? Version: 2.8.3 -alok

3 years, 2 months

2
3
0 / 0

Change in ...nfs-ganesha[next]: Add atomic_add_unless and PTHREAD_MUTEX_decrement_XXX_t_and_lock

by Frank Filz (GerritHub)

Frank Filz has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/524203 ) Change subject: Add atomic_add_unless and PTHREAD_MUTEX_decrement_XXX_t_and_lock ...................................................................... Add atomic_add_unless and PTHREAD_MUTEX_decrement_XXX_t_and_lock Change-Id: I70dd0ab1296b27d87e5abe45e08a3b591a2fcee5 Signed-off-by: Frank S. Filz <ffilzlnx(a)mindspring.com> --- M src/include/abstract_atomic.h A src/include/atomic_utils.h 2 files changed, 314 insertions(+), 1 deletion(-) git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/03/524203/1 -- To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/524203 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: I70dd0ab1296b27d87e5abe45e08a3b591a2fcee5 Gerrit-Change-Number: 524203 Gerrit-PatchSet: 1 Gerrit-Owner: Frank Filz <ffilzlnx(a)mindspring.com> Gerrit-MessageType: newchange

3 years, 3 months

1
0
0 / 0

Change in ...nfs-ganesha[next]: Remove duplicate code

by xijinyu (GerritHub)

xijinyu has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/524147 ) Change subject: Remove duplicate code ...................................................................... Remove duplicate code Signed-off-by: Xi Jinyu <xijinyu0811(a)163.com> Change-Id: I81e214fdef609c09138890730a94a7641a83d994 --- M src/FSAL/FSAL_GPFS/fsal_mds.c 1 file changed, 0 insertions(+), 1 deletion(-) git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/47/524147/1 -- To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/524147 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: I81e214fdef609c09138890730a94a7641a83d994 Gerrit-Change-Number: 524147 Gerrit-PatchSet: 1 Gerrit-Owner: xijinyu <xijinyu0811(a)163.com> Gerrit-MessageType: newchange

3 years, 3 months

1
0
0 / 0

Change in ...nfs-ganesha[next]: As per the RFC#5661, in the cluster enviroment, the server should ret...

by Name of user not set (GerritHub)

prabhu.murugeshan(a)ibm.com has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/523742 ) Change subject: As per the RFC#5661, in the cluster enviroment, the server should return server_scope string which is common across all the NFS server in the cluster. The NFS client will use server_scope to reclaim locks if there is a failover from one server to another. ...................................................................... As per the RFC#5661, in the cluster enviroment, the server should return server_scope string which is common across all the NFS server in the cluster. The NFS client will use server_scope to reclaim locks if there is a failover from one server to another. Currently, we are returing hostname as server_scope (in exchange id request) which is wrong. Added new config parameter server_scope in ganesha.main.conf and it is settable value. The preferred value for server_scope is clustername. Change-Id: I1ce49bac3ada0e9166491fbfce8528448ad279c2 Signed-off-by: Prabhu Murugesan <prabhu.murugeshan(a)ibm.com> --- M src/Protocols/NFS/nfs4_op_exchange_id.c M src/include/gsh_config.h M src/support/nfs_read_conf.c 3 files changed, 23 insertions(+), 1 deletion(-) git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/42/523742/1 -- To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/523742 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: I1ce49bac3ada0e9166491fbfce8528448ad279c2 Gerrit-Change-Number: 523742 Gerrit-PatchSet: 1 Gerrit-Owner: prabhu.murugeshan(a)ibm.com Gerrit-MessageType: newchange

3 years, 3 months

1
0
0 / 0

Weekly Tuesday community call changes

by Frank Filz

We are moving to Google Meet to host the community meetings. I have sent a Google invite to the mailing list, or use this URL: https://meet.google.com/mkh-ctnj-tqz Phone numbers for dialing are available here: https://tel.meet/mkh-ctnj-tqz?pin=2844708468265 <https://tel.meet/mkh-ctnj-tqz?pin=2844708468265&hs=0> &hs=0 Due to my schedule changing the meetings will be limited to 30 minutes. At the next meeting we can discuss changing the time, otherwise it will be at the same 7:00 AM Pacific Time starting time. Maybe we'll try and hold off changing it until the time is forced to change by the ending of Daylight Saving Time in October. Frank

3 years, 3 months

1
0
0 / 0

Invitation: Ganesha community call @ Weekly from 7am to 7:30am on Tuesday (PDT) (devel@lists.nfs-ganesha.org)

by ffilz＠redhat.com

You have been invited to the following event. Title: Ganesha community call When: Weekly from 7am to 7:30am on Tuesday Pacific Time - Los Angeles Joining info: Join with Google Meet https://meet.google.com/mkh-ctnj-tqz?hs=224 Join by phone (US) +1 401-702-0462 (PIN: 495972631) Join using SIP 2844708468265(a)gmeet.redhat.com (ID: 2844708468265) More joining options: https://tel.meet/mkh-ctnj-tqz?pin=2844708468265&hs=0 Calendar: devel(a)lists.nfs-ganesha.org Who: * ffilz(a)redhat.com - organizer * devel(a)lists.nfs-ganesha.org Event details: https://calendar.google.com/calendar/event?action=VIEW&eid=NXZubmZhbGJwcT... Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this courtesy email at the account devel(a)lists.nfs-ganesha.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://calendar.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding

3 years, 3 months

1
0
0 / 0

Change in ...nfs-ganesha[next]: Change from default of 1 second for time_delta to 100 ns.

by Frank Filz (GerritHub)

Frank Filz has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/523405 ) Change subject: Change from default of 1 second for time_delta to 100 ns. ...................................................................... Change from default of 1 second for time_delta to 100 ns. Set the default time_delta value in a constant to make it easy to change. There doesn't seem to be a good way of getting a true value for this, even with the PROXY FSALs (PROXY_V3 was using invarsec from FSSTAT which is only seconds and not ns, and PROXY_V4 for sure isn't decoding time_delta and may not be asking for it). The previous global default of 1 second is causing issues with at least one client throwing scary sounding warning messages and maybe changing behavior. We chose 100 ns as a "reasonable" default that doesn't overstate the resolution but also doens't make us look bad in some way. There is reasonable arguments for anything from 1 ns to 1 ms. Interestingly FSAL_KVSFS doesn't fill ANYTHING in for get_dynamic_info which probably is not good but I don't know anything about kvfsf to have any idea what to do there but a todo comment seems in order. Change-Id: Ibf43dfe9d970b908bf05ef699d45fe3bcafc3b7b Signed-off-by: Frank S. Filz <ffilzlnx(a)mindspring.com> --- M src/FSAL/FSAL_CEPH/export.c M src/FSAL/FSAL_GLUSTER/export.c M src/FSAL/FSAL_GPFS/export.c M src/FSAL/FSAL_KVSFS/kvsfs_export.c M src/FSAL/FSAL_LIZARDFS/export.c M src/FSAL/FSAL_MEM/mem_export.c M src/FSAL/FSAL_PROXY_V3/main.c M src/FSAL/FSAL_PROXY_V4/handle.c M src/FSAL/FSAL_PSEUDO/export.c M src/FSAL/FSAL_RGW/export.c M src/FSAL/FSAL_VFS/export.c M src/include/fsal_types.h 12 files changed, 37 insertions(+), 18 deletions(-) git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/05/523405/1 -- To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/523405 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: Ibf43dfe9d970b908bf05ef699d45fe3bcafc3b7b Gerrit-Change-Number: 523405 Gerrit-PatchSet: 1 Gerrit-Owner: Frank Filz <ffilzlnx(a)mindspring.com> Gerrit-MessageType: newchange

3 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

Devel September 2021