[Nfs-ganesha-devel] nfs ganesha centos ci tests - posix compliance
Hi All, I have added new test in upstream nfs-ganesha centos ci which runs posix compliance test suite on v3 and v4 mount. Centos ci job link - https://ci.centos.org/view/NFS-Ganesha/job/nfs_ganesha_posix_compliance/ The job gets triggered automatically for every patchset created and reports back the result. Please try using the job and share your comments. Thanks & Regards, Arthy -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: minor changes to build on openSUSE Leap
>From :
ka...@redhat.com has uploaded this change for review. (
https://review.gerrithub.io/366456
Change subject: minor changes to build on openSUSE Leap
..
minor changes to build on openSUSE Leap
Need distribution-release so that cmake can get NAME="openSUSE Leap"
from /etc/os-release. (Somehow it manages to work on SLES 12.)
Don't {,Build}Requires: sles-release for openSUSE.
Change-Id: I59415362bd68ffcea7f7057b9d3e7f89c5aff5d7
Signed-off-by: Kaleb S. KEITHLEY
---
M src/CMakeLists.txt
M src/nfs-ganesha.spec-in.cmake
2 files changed, 7 insertions(+), 0 deletions(-)
git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha
refs/changes/56/366456/1
--
To view, visit https://review.gerrithub.io/366456
To unsubscribe, visit https://review.gerrithub.io/settings
Gerrit-Project: ffilz/nfs-ganesha
Gerrit-Branch: next
Gerrit-MessageType: newchange
Gerrit-Change-Id: I59415362bd68ffcea7f7057b9d3e7f89c5aff5d7
Gerrit-Change-Number: 366456
Gerrit-PatchSet: 1
Gerrit-Owner: ka...@redhat.com
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] timed waits
You're welcome to make it an ntirpc init parameter. Matt - Original Message - > From: "Daniel Gryniewicz" > To: nfs-ganesha-devel@lists.sourceforge.net > Sent: Wednesday, June 21, 2017 8:13:34 AM > Subject: Re: [Nfs-ganesha-devel] timed waits > > On 06/21/2017 05:26 AM, William Allen Simpson wrote: > > I'd thought my Ganesha wasn't shutting down properly. Turned out to > > be sitting in several timed waits: fridge, epoll. > > > > The EPOLL timeout is 120 seconds, but has "XXX" next to it. Apparently, > > others are that long elsewhere, too. Seems a long time. > > > > Is there a configuration parameter somewhere to use instead? > > There doesn't seem to be, no. > > Daniel > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Nfs-ganesha-devel mailing list > Nfs-ganesha-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel > -- Matt Benjamin Red Hat, Inc. 315 West Huron Street, Suite 140A Ann Arbor, Michigan 48103 http://www.redhat.com/en/technologies/storage tel. 734-821-5101 fax. 734-769-8938 cel. 734-216-5309 -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] Community packages of nfs-ganesha-2.5.0 are available
On 06/15/2017 06:28 AM, Kaleb S. KEITHLEY wrote: > > RPM and .deb packages of nfs-ganesha-2.5 are available for several > popular linux distributions: > > * Packages are in Fedora 26 and Fedora 27/rawhide. Use `dnf install ...` > Packages will be in the Fedora 26 Updates-Testing repo for a short while > before being promoted to the Updates repo. > > * Packages for Fedora 25 are available in the repo at [1] > > * Packages for Ubuntu Xenial (16.04), Yakkety (16.10), and Zesty (17.04) > are in the Ubuntu Launchpad PPA at [2] > > * Packages for Debian Jessie (8) and Stretch/Sid (9) are in a repo at [1] > > * Packages for CentOS will be in the CentOS Storage SIG shortly. Info on > the CentOS Storage SIG is at [3]. > > * Packages for SLES 12 and Leap 42 are almost ready but I have some > packaging nits to resolve. I will send an updated announcement when they > are ready. Packages for SLES12 and OpenSuSE Leap 42 are now available at [7]. > > FSAL coverage is mixed and depends on the prerequisites that are > available in the particular distribution. Most packages include the > basic FSALS, e.g. xfs, vfs, null, etc. Where possible they include > Gluster, Ceph, and Ceph RGW. If using gluster, glusterfs-3.10.x or later > is required. > > Community packages are provided as is, as a convenience for the > community. They are not "official" packages. In fact you may find that > your linux distribution provides its own packages, usually of an earlier > version than provided by the NFS-Ganesha community. > > If you find problems with the *packaging* you may file a BZ for > Fedora/CentOS/RHEL packages at [4] or open a github issue for > Debian/Ubuntu packages at [5]. > > If you find problems with nfs-ganesha itself, you may file a BZ at [4] > or open a github issue at [6] > > [1] https://download.gluster.org/pub/gluster/nfs-ganesha/2.5/ > [2] https://launchpad.net/~gluster/+archive/ubuntu/nfs-ganesha-2.5 > [3] https://wiki.centos.org/SpecialInterestGroup/Storage > [4] https://bugzilla.redhat.com/enter_bug.cgi?product=nfs-ganesha > [5] https://github.com/nfs-ganesha/nfs-ganesha-debian/issues > [6] https://github.com/nfs-ganesha/nfs-ganesha/issues [7] https://build.opensuse.org/project/subprojects/home:glusterfs -- Kaleb -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] timed waits
On 06/21/2017 05:26 AM, William Allen Simpson wrote: I'd thought my Ganesha wasn't shutting down properly. Turned out to be sitting in several timed waits: fridge, epoll. The EPOLL timeout is 120 seconds, but has "XXX" next to it. Apparently, others are that long elsewhere, too. Seems a long time. Is there a configuration parameter somewhere to use instead? There doesn't seem to be, no. Daniel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] cache and hash and partitions should be primes
hi bill, inline - Original Message - > From: "William Allen Simpson" > To: "NFS Ganesha Developers" > Sent: Wednesday, June 21, 2017 4:01:01 AM > Subject: [Nfs-ganesha-devel] cache and hash and partitions should be primes > > Was looking through ntirpc cache/hash sizes, and discovered that: > svc_auth_des.c has 64 (not prime); not used? > authgss_hash.c has 255 (not prime). good catch > > Configurable number of partitions aren't checked for primality. > > So began checking Ganesha as well. > > src/support/export_mgr.c has a nice size of 769, appropriate for > 10,000'ish exports by id with a hit rate of 0.130208. > > src/support/ds.c has a fair size of 163, appropriate for 256'ish > active servers with a hit rate of 0.520833. > > (I chose those two a couple of years ago.) > > The number 1009 is used several places. Prime, but too large? > src/support/netgroup_cache.c > src/support/uid2grp_cache.c > src/idmapper/idmapper_cache.c > > DRC_TCP_CACHESZ 127 and DRC_UDP_CACHESZ 599, while prime, seem > completely oddball (and reversed). And allow configuration to 255 > and 2047 (not prime) respectively. careful; first is small on the theory it will retire fast, and note it is per connection the UDP DRC is global, so larger Matt > > Are there others that I've missed? > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Nfs-ganesha-devel mailing list > Nfs-ganesha-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel > -- Matt Benjamin Red Hat, Inc. 315 West Huron Street, Suite 140A Ann Arbor, Michigan 48103 http://www.redhat.com/en/technologies/storage tel. 734-821-5101 fax. 734-769-8938 cel. 734-216-5309 -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
[Nfs-ganesha-devel] timed waits
I'd thought my Ganesha wasn't shutting down properly. Turned out to be sitting in several timed waits: fridge, epoll. The EPOLL timeout is 120 seconds, but has "XXX" next to it. Apparently, others are that long elsewhere, too. Seems a long time. Is there a configuration parameter somewhere to use instead? -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] Proxy Problems 2.5
On 06/20/17 15:41, Frank Filz wrote:
On 06/19/2017 05:22 AM, LUCAS Patrice wrote:
On 06/16/17 15:21, Frank Filz wrote:
On 06/15/17 21:34, Doug Ortega wrote:
Frank,
Turns out that the nfs-ganesha proxy client was using a source port
1024 for the nfs client connection to the server. I added the
'insecure' option to export in /etc/exports on the server to allow
client connections from an unreserved source port. This let me get
past the issue with the NFS4ERR_PERM being returned on the lookup.
Doug
---
---
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Hi Doug,
By default, it's true that the nfs-ganesha proxy client is using a
source port >
1024 to connect the background nfs server. You have an option to
change this. If you want the proxy client use a privileged port, you
should use the Use_Privileged_Client_Port option as this :
PROXY
{
Remote_Server
{
Srv_Addr=192.168.1.30;
Use_Privileged_Client_Port = true;
}
}
Let me know if you are facing any problem by using this option. I
will be happy to try to fix it.
Hmm, should we change the default to true?
Frank
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
If everyone agrees, I can submit a patch that use a privileged port by
default for the FSAL_PROXY client to connect the background NFS server.
Let me know and I will do it.
I'm fine with this. If someone wants to run proxy as non-root, they can
change this setting.
Agreed.
Frank
Patch done for the Use_Privileged_Client_Port FSAL_PROXY option :
https://review.gerrithub.io/#/c/366391/ .
What about the PrivilegedPort option and this old patch
https://review.gerrithub.io/#/c/288895/ ?
Best regards,
Patrice
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: FSAL_PROXY : Use_Privileged_Client_Port default from false t...
>From Patrice LUCAS : Patrice LUCAS has uploaded this change for review. ( https://review.gerrithub.io/366391 Change subject: FSAL_PROXY : Use_Privileged_Client_Port default from false to true .. FSAL_PROXY : Use_Privileged_Client_Port default from false to true By changing this default parameter value, the FSAL_PROXY uses by default a privileged port to connect the background NFS server and must be executed as root by default. Change-Id: Ia7c8890536af5bf47bfbdb6254430401075aaee3 Signed-off-by: Patrice LUCAS --- M src/FSAL/FSAL_PROXY/main.c M src/config_samples/config.txt M src/doc/man/ganesha-proxy-config.rst 3 files changed, 3 insertions(+), 3 deletions(-) git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/91/366391/1 -- To view, visit https://review.gerrithub.io/366391 To unsubscribe, visit https://review.gerrithub.io/settings Gerrit-Project: ffilz/nfs-ganesha Gerrit-Branch: next Gerrit-MessageType: newchange Gerrit-Change-Id: Ia7c8890536af5bf47bfbdb6254430401075aaee3 Gerrit-Change-Number: 366391 Gerrit-PatchSet: 1 Gerrit-Owner: Patrice LUCAS -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
[Nfs-ganesha-devel] cache and hash and partitions should be primes
Was looking through ntirpc cache/hash sizes, and discovered that: svc_auth_des.c has 64 (not prime); authgss_hash.c has 255 (not prime). Configurable number of partitions aren't checked for primality. So began checking Ganesha as well. src/support/export_mgr.c has a nice size of 769, appropriate for 10,000'ish exports by id with a hit rate of 0.130208. src/support/ds.c has a fair size of 163, appropriate for 256'ish active servers with a hit rate of 0.520833. (I chose those two a couple of years ago.) The number 1009 is used several places. Prime, but too large? src/support/netgroup_cache.c src/support/uid2grp_cache.c src/idmapper/idmapper_cache.c DRC_TCP_CACHESZ 127 and DRC_UDP_CACHESZ 599, while prime, seem completely oddball (and reversed). And allow configuration to 255 and 2047 (not prime) respectively. Are there others that I've missed? -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
