January 2022 - Devel - Nfs Ganesha List Archives

Change in ...nfs-ganesha[next]: Bugfix: Allow listening on TCP only without IPv6 configured

by Idan Yadgar (GerritHub)

Idan Yadgar has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/530706 ) Change subject: Bugfix: Allow listening on TCP only without IPv6 configured ...................................................................... Bugfix: Allow listening on TCP only without IPv6 configured In src/MainNFSD/nfs_rpc_dispatcher_thread.c we handled the case of not having IPv6 configured when trying to create a UDPv6 socket. If we get `errno == EAFNOSUPPORT` (Address family not supported by protocol), we assume IPv6 is not configured, and we know not to try to create a TCPv6 socket. We know that if we try to create a TCPv6 socket, it cannot fail, because IPv6 must be configured (if it wasn't, we would fail with UDPv6 and would not try TCPv6). The bug is that if `Enable_UDP = false` was specified in the config, we will not try to create UDP sockets, and we will get `errno == EAFNOSUPPORT` for the first time when creating the TCP sockets, and then we will exit. The fix is to check if `Enable_UDP = false` was set when we fail to create a TCPv6 socket. If it was, we know that this is the first IPv6 socket we try to create, and we understand that IPv6 is not configured, so we move on to use IPv4 only. Change-Id: I4687bfb325e7c134369d6438d9f77f0b11ba664f Signed-off-by: Idan Yadgar <idanyadgar(a)gmail.com> --- M src/MainNFSD/nfs_rpc_dispatcher_thread.c 1 file changed, 45 insertions(+), 12 deletions(-) git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/06/530706/1 -- To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/530706 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: I4687bfb325e7c134369d6438d9f77f0b11ba664f Gerrit-Change-Number: 530706 Gerrit-PatchSet: 1 Gerrit-Owner: Idan Yadgar <idanyadgar(a)gmail.com> Gerrit-MessageType: newchange

2 years, 10 months

1
0
0 / 0

Change in ...nfs-ganesha[next]: Do not define nfsv3_optype if NFS3 is not configured

by Idan Yadgar (GerritHub)

Idan Yadgar has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/530705 ) Change subject: Do not define nfsv3_optype if NFS3 is not configured ...................................................................... Do not define nfsv3_optype if NFS3 is not configured Change-Id: I090e5821b5b65f4c5a31f073db303b2b78436c4d Signed-off-by: Idan Yadgar <idanyadgar(a)gmail.com> --- M src/support/server_stats.c 1 file changed, 12 insertions(+), 0 deletions(-) git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/05/530705/1 -- To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/530705 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: I090e5821b5b65f4c5a31f073db303b2b78436c4d Gerrit-Change-Number: 530705 Gerrit-PatchSet: 1 Gerrit-Owner: Idan Yadgar <idanyadgar(a)gmail.com> Gerrit-MessageType: newchange

2 years, 10 months

1
0
0 / 0

Re: NFS testing

by Frank Filz

I'm embarrassed that I don't do anything close to this for my weekly nfs-ganesha merges... I'd love to see some tools to make it easier to do more testing. I wish there was a solution that didn't require two hosts for testing NFSv3 locks against nfs-ganesha. I need to get back to the pynfs v3 tests... Another test I have run is pjdfstests, which there seem to be multiple versions of, I have repos of two versions here that are Ganesha aware. These tests include a lot of POSIX compliance so will catch permission issues and other POSIX oddities. I also haven't run them in ages... https://github.com/ffilz/ntfs-3g-pjd-fstest https://github.com/ffilz/pjdfstest The nfs-ganesha tree also has a tool to help write lock tests (and can be used for a few other things too - I recently added more flags to open so it can test most open system call invocations of interest) in: https://github.com/nfs-ganesha/nfs-ganesha/tree/next/src/tools/multilock Hmm, I should incorporate the features of Bruce's lock tests into that... The multilock tool can drive multiple clients to use system calls (so any POSIX client can be used including a local process on the server) or Gluster's libgfapi or Cephs libcephfs. Frank > -----Original Message----- > From: J. Bruce Fields [mailto:bfields@fieldses.org] > Sent: Friday, January 7, 2022 1:35 PM > To: Chuck Lever <chuck.lever(a)oracle.com> > Cc: linux-nfs(a)vger.kernel.org > Subject: NFS testing > > Chuck was asking about the regular NFS testing I do. Cc'ing the list in case this is > useful to anyone else. > > We'd really like to set up regular testing on some kind of common infrastructure > that more people can get to. I'm not sure how to get there yet. > > For now all I have is this pile of bash scripts that build kernels and boot test VMs > and run tests between them, all on a machine in my > basement: > > http://git.linux-nfs.org/?p=bfields/testd.git;a=tree > > The "install.sh" file has notes on my setup. > > The thing I run most regularly is this: > > http://git.linux-nfs.org/?p=bfields/testd.git;a=blob;f=bin/do-all > > which runs: > > - connectathon, on v3, v4, v4.1, and v4.2, each with both > auth_sys and krb5. Except v4.2, which I run with auth_sys, > krb5i, and krb5p. > - at the same time as connectathon (so with the same > permutations as the above), I also run the tests in > > http://git.linux-nfs.org/?p=bfields/lock-tests.git > > which check basic lock and lease functionality plus some odd > corner cases I ran into some years ago. > - pynfs 4.0 tests: > http://git.linux-nfs.org/?p=bfields/testd.git;a=blob;f=bin/do- > pynfs > I do two auth_sys runs, one as root, one not. (Tests that > create special files need root, tests that expect permission > failures need non-root). A couple krb5 runs are temporarily > disabled. > > My goal is that a normal result should be "everything passed", > so that it stands out when there's a regression. So I skip a > few known failures: > http://git.linux- > nfs.org/?p=bfields/testd.git;a=blob;f=data/pynfs-skip > - pynfs 4.1 tests: similar if a little less complicated: > http://git.linux-nfs.org/?p=bfields/testd.git;a=blob;f=bin/do- > pynfs41 > 4.1 tests to skip: > http://git.linux- > nfs.org/?p=bfields/testd.git;a=blob;f=data/pynfs41-skip > - xfstests: > http://git.linux-nfs.org/?p=bfields/testd.git;a=blob;f=bin/do- > xfstests > This is the most time-consuming, so I just do a single run > over NFSv4.2 with auth_sys. > > As with pynfs I aim for the normal result to be "everything > passed", so I skip these known failures: > http://git.linux- > nfs.org/?p=bfields/testd.git;a=blob;f=data/xfstests-failed > I also normally skip anything that takes more than a couple > minutes, unfortunately: > http://git.linux- > nfs.org/?p=bfields/testd.git;a=blob;f=data/xfstests-slow > > I also have some other test sets in there that I don't use as often. > And I "bisect" script that will run other tests, e.g. > > qtst <host> bisect <good> <bad> xfstests generic/465 > > and it'll crank away for a few hours and (hopefully) mail me a git-bisect result > telling me where generic/465 started failing. > > --b.

2 years, 10 months

1
0
0 / 0

Change in ...nfs-ganesha[next]: Limit the number of entries in a readdir response to 4 x chunk size

by Frank Filz (GerritHub)

Frank Filz has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/530500 ) Change subject: Limit the number of entries in a readdir response to 4 x chunk size ...................................................................... Limit the number of entries in a readdir response to 4 x chunk size Change-Id: Ia182fc337b401987cc4f70fad8919d026fe46742 Signed-off-by: Frank S. Filz <ffilzlnx(a)mindspring.com> --- M src/FSAL/Stackable_FSALs/FSAL_MDCACHE/mdcache_read_conf.c M src/FSAL/Stackable_FSALs/FSAL_MDCACHE/mdcache_helpers.c M src/FSAL/Stackable_FSALs/FSAL_MDCACHE/mdcache_ext.h 3 files changed, 22 insertions(+), 1 deletion(-) git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/00/530500/1 -- To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/530500 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: Ia182fc337b401987cc4f70fad8919d026fe46742 Gerrit-Change-Number: 530500 Gerrit-PatchSet: 1 Gerrit-Owner: Frank Filz <ffilzlnx(a)mindspring.com> Gerrit-MessageType: newchange

2 years, 10 months

1
0
0 / 0

Re: ganesha debus server thread hang after creating 20K nfs shares

by Daniel Gryniewicz

There's no built-in limit, everything is expandable lists. However, you'll certainly run out of memory at some point, and searching linked lists degrades in performance as they get larger, so there's certainly limits somewhere. I highly doubt anyone has come close to 50k exports before. You're backtrace is parsing the config file, so maybe large config file parsing becomes slow? Daniel On 12/25/21 05:12, bbjjffmcxs(a)outlook.com wrote: > Dear maintainer， > > Does ganesha have a limit on the number of nfs share? > > Recently I attempted to create 50 thousand nfs shares and it > turned out the debus server thread got stuck after creating about 20K > shares. > > Also the commad “ganesha_mgr show exports” got no reponse and > finally timed out. See the below detailed result. > > Could you please help take a took and give your valuable advice? > > Thanks a lot. > > Attahed the backtrace below. > > --------------env----------- > > NFS-Ganesha Release = V3.5 > > ------------------Backtrace----------- > > #0 0x00007ff0425ed7f4 in __strcasecmp_l_avx () from /lib64/libc.so.6 > > #1 0x00007ff044dcaabd in save_token (token=0x7ff00d5f0262 > "No_Root_Squash", esc=false, st=0x7ff0203befd0) at > /usr/src/debug/nfs-ganesha-3.5/config_parsing/analyse.c:60 > > #2 0x00007ff044dd4214 in ganeshun_yylex (yylval_param=0x7ff0203bef20, > yylloc_param=0x7ff0203bef00, yyscanner=0x7ff008874080) at > /usr/src/debug/nfs-ganesha-3.5/config_parsing/conf_lex.l:364 > > #3 0x00007ff044dd1daf in ganesha_yylex (yylval_param=0x7ff0203bef20, > yylloc_param=0x7ff0203bef00, st=0x7ff0203befd0) at > /usr/src/debug/nfs-ganesha-3.5/config_parsing/conf_yacc.y:520 > > #4 0x00007ff044dd09c5 in ganesha_yyparse (st=0x7ff0203befd0) at > /usr/src/debug/nfs-ganesha-3.5/config_parsing/conf_yacc.c:1407 > > #5 0x00007ff044dcb6cc in config_ParseFile (file_path=0x7ff0091260b4 > "/etc/ganesha/ganesha.conf", err_type=0x7ff0203bf0d0) at > /usr/src/debug/nfs-ganesha-3.5/config_parsing/config_parsing.c:60 > > #6 0x00007ff044e4f803 in gsh_export_addexport (args=0x7ff0203bf1a0, > reply=0x7ff008874200, error=0x7ff0203bf1f0) at > /usr/src/debug/nfs-ganesha-3.5/support/export_mgr.c:1057 > > #7 0x00007ff044ee360a in dbus_message_entrypoint (conn=0x7ff03f4d9580, > msg=0x7ff0088742c0, user_data=0x7ff04518dd10 <export_interfaces>) at > /usr/src/debug/nfs-ganesha-3.5/dbus/dbus_server.c:574 > > #8 0x00007ff0446d6466 in _dbus_object_tree_dispatch_and_unlock () from > /lib64/libdbus-1.so.3 > > #9 0x00007ff0446c7d19 in dbus_connection_dispatch () from > /lib64/libdbus-1.so.3 > > #10 0x00007ff0446c8032 in _dbus_connection_read_write_dispatch () from > /lib64/libdbus-1.so.3 > > #110x00007ff044ee42b5 in gsh_dbus_thread (arg=0x0) at > /usr/src/debug/nfs-ganesha-3.5/dbus/dbus_server.c:810 > > #12 0x00007ff042ea4ea5 in start_thread () from /lib64/libpthread.so.0 > > #13 0x00007ff0425a396d in clone () from /lib64/libc.so.6 > > 从Windows 版邮件 <https://go.microsoft.com/fwlink/?LinkId=550986>发送 > > > _______________________________________________ > Devel mailing list -- devel(a)lists.nfs-ganesha.org > To unsubscribe send an email to devel-leave(a)lists.nfs-ganesha.org

2 years, 10 months

2
1
0 / 0

Re: [nfs-ganesha/nfs-ganesha] Release V4.0 - NFS-Ganesha 4.0 GA

by Kaleb Keithley

On Wed, Dec 22, 2021 at 4:24 AM Yaniv Kaul <ykaul(a)redhat.com> wrote: > Trying to compile on my F35, following > https://github.com/nfs-ganesha/nfs-ganesha/blob/next/src/COMPILING_HOWTO.txt > : > > -- Configuring done > CMake Error: The following variables are used in this project, but they > are set to NOTFOUND. > Please set them or make sure they are set and tested correctly in the > CMake files: > NSL_LIBRARY (ADVANCED) > linked by target "ntirpc" in directory > /home/tlv/ykaul/github/nfs-ganesha/src/libntirpc/src > > -- Generating done > I personally usually use this: `cmake . -DCMAKE_BUILD_TYPE=RelWithDebInfo -DBUILD_CONFIG=rpmbuild -DUSE_FSAL_NULL=on -DUSE_FSAL_MEM=on -DUSE_FSAL_XFS=on -DUSE_FSAL_LUSTRE=off -DUSE_FSAL_CEPH=off -DUSE_FSAL_RGW=off -DUSE_FSAL_GPFS=on -DUSE_FSAL_PANFS=off -DUSE_FSAL_GLUSTER=on -DUSE_SYSTEM_NTIRPC=on -DUSE_9P_RDMA=off -DUSE_LTTNG=off -DUSE_ADMIN_TOOLS=off -DUSE_GUI_ADMIN_TOOLS=off -DUSE_RADOS_RECOV=off -DRADOS_URLS=off -DUSE_FSAL_VFS=ON -DUSE_FSAL_PROXY_V4=on -DUSE_FSAL_PROXY_V3=on -DUSE_DBUS=ON -DUSE_9P=off -DDISTNAME_HAS_GIT_DATA=OFF -DUSE_MAN_PAGE=off -DRPCBIND=on -D_MSPAC_SUPPORT=off -DSANITIZE_ADDRESS=off` If you install the ceph dependencies, you can change -DUSE_FSAL_CEPH=off -DUSE_FSAL_RGW=off -DUSE_RADOS_RECOV=off -DRADOS_URLS=off to "on" But even, e.g., just `cmake . -DCMAKE_BUILD_TYPE=Maintainer` should work. (It did work for me recently.) It will at least build FSAL_VFS, which is enough to run a basic NFS server serving local file systems. > > Trying > https://github.com/nfs-ganesha/nfs-ganesha/blob/6156de38f0179b473942a1532... > fails as well: > [ykaul@ykaul build_dir]$ CC=clang cmake -i ~/github/nfs-ganesha/src > The "cmake -i" wizard mode is no longer supported. > Use the -D option to set cache values on the command line. > Use cmake-gui or ccmake for an interactive dialog. > > We haven't ever tried using clang AFAIK, at least not at Red Hat on Linux. This release did get some attention from the FreeBSD community though, so I would not be surprised if it just worked. I've never used cmake wizard mode. > > In short, I would be happy to update the docs once I solve those issues. > Y. > > On Wed, Dec 22, 2021 at 12:04 AM Kaleb Keithley <kkeithle(a)redhat.com> > wrote: > >> https://github.com/nfs-ganesha/nfs-ganesha/wiki/ReleaseNotes_4 >> >> On Tue, Dec 21, 2021 at 4:30 PM Yaniv Kaul <ykaul(a)redhat.com> wrote: >> >>> Congrats, where's the ChangeLog? Something to celebrate? >>> Y. >>> >>> On Tue, Dec 21, 2021 at 11:09 PM kalebskeithley < >>> notifications(a)github.com> wrote: >>> >>>> NFS-Ganesha 4.0 GA >>>> <https://github.com/nfs-ganesha/nfs-ganesha/releases/tag/V4.0> >>>> >>>> Repository: nfs-ganesha/nfs-ganesha >>>> <https://github.com/nfs-ganesha/nfs-ganesha> · Tag: V4.0 >>>> <https://github.com/nfs-ganesha/nfs-ganesha/tree/V4.0> · Commit: >>>> 6156de3 >>>> <https://github.com/nfs-ganesha/nfs-ganesha/commit/6156de38f0179b473942a15...> >>>> · Released by: kalebskeithley <https://github.com/kalebskeithley> >>>> >>>> NFS-Ganesha 4.0 GA >>>> — >>>> >>>> This release has 2 assets: >>>> >>>> - Source code (zip) >>>> - Source code (tar.gz) >>>> >>>> Visit the release page >>>> <https://github.com/nfs-ganesha/nfs-ganesha/releases/tag/V4.0> to >>>> download them. >>>> >>>> — >>>> You are receiving this because you are watching this repository. >>>> View it on GitHub >>>> <https://github.com/nfs-ganesha/nfs-ganesha/releases/tag/V4.0> or >>>> unsubscribe >>>> <https://github.com/nfs-ganesha/nfs-ganesha/unsubscribe_via_email/ABDQT2KU...> >>>> from all notifications for this repository. >>>> >>> >> >> -- >> >> Kaleb >> > -- Kaleb

2 years, 10 months

4
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

Devel January 2022