Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
02-17-2014, 07:04 PM
|
#1
|
Member
Registered: Aug 2006
Distribution: Slackware, OpenBSD, CentOS, Ubuntu
Posts: 99
Rep:
|
14.1 NFS v4 30 seconds to open a file
I upgraded from 14.0 this weekend and found that Debian could no longer access my shares. After much debugging, it looks like it's taking 30 seconds to open a file. Here's the export on my Slackware server:
Code:
/home/kent/Music lms(secure,ro,all_squash,sync,no_subtree_check)
And here's the fstab entry on Debian:
Code:
hex:/home/kent/Music /home/lms/Music nfs sync,nodev,noatime,nodiratime,noexec,nosuid,ro 0 0
Tried on Squeeze and Wheezy, and both have the same problem with 14.1. No problem at all with 14.0. Solved for now by adding nfsvers=3 to fstab.
Am I doing something wrong, or is this just a bad regression?
|
|
|
02-17-2014, 07:07 PM
|
#2
|
LQ Sage
Registered: Nov 2004
Location: Saint Amant, Acadiana
Distribution: Gentoo ~amd64
Posts: 7,675
Rep:
|
Shot in the dark, but such delays are most often caused by failed NS lookups.
|
|
|
02-18-2014, 02:52 AM
|
#3
|
Member
Registered: Apr 2009
Location: Oz
Distribution: slackware64-14.0
Posts: 875
|
Slackware's nfs-utils are not compiled with nfs4 support turned on, though the kernel does have it.
That alone could cause issues when dealing with a distro that is fully nfs4 enabled.
|
|
2 members found this post helpful.
|
02-18-2014, 09:08 AM
|
#4
|
Member
Registered: Aug 2006
Distribution: Slackware, OpenBSD, CentOS, Ubuntu
Posts: 99
Original Poster
Rep:
|
Quote:
Shot in the dark, but such delays are most often caused by failed NS lookups.
|
Client is in my /etc/hosts, and there's no lookups apparent in a tcpdump from the server.
Quote:
Slackware's nfs-utils are not compiled with nfs4 support turned on, though the kernel does have it.
|
I noticed when I connected from a Slackware client it was all V3. That's what gave me the idea to downgrade the version. Debian connects V4 by default to both 14.0 (works fine) and 14.1 (30 seconds to open a file).
|
|
|
02-18-2014, 01:56 PM
|
#5
|
Senior Member
Registered: Sep 2009
Location: Leinster, IE
Distribution: Slackware, NetBSD
Posts: 2,226
|
Quote:
Originally Posted by kfritz
Client is in my /etc/hosts, and there's no lookups apparent in a tcpdump from the server.
I noticed when I connected from a Slackware client it was all V3. That's what gave me the idea to downgrade the version. Debian connects V4 by default to both 14.0 (works fine) and 14.1 (30 seconds to open a file).
|
Are you using UDP or TCP for your NFS mounts?
|
|
|
02-22-2014, 12:53 PM
|
#6
|
Member
Registered: Aug 2006
Distribution: Slackware, OpenBSD, CentOS, Ubuntu
Posts: 99
Original Poster
Rep:
|
I investigated a bit deeper, and it looks like wildwizard was pointing in the right direction. I enabled CONFIG_SUNRPC_DEBUG in my config and recompiled the kernel, and then used "rpcdebug -m nfsd -s all", and modified /etc/syslog to capture the debug into /var/log/debug. What shows up at the 30 second delay is:
Quote:
Feb 22 07:26:25 sl64-14-1 kernel: [ 815.614593] NFSD: nfsd4_open_confirm: success, seqid=1 stateid=(5308bf1a/00000003/00000000/00000002)
Feb 22 07:26:25 sl64-14-1 kernel: [ 815.614595] alloc_cld_upcall: allocated xid 3
Feb 22 07:26:55 sl64-14-1 kernel: [ 845.664090] NFSD: Unable to create client record on stable storage: -110
Feb 22 07:26:55 sl64-14-1 kernel: [ 845.664096] nfsv4 compound op ffff88003d3fa080 opcnt 2 #2: 20: status 0
|
That timeout error comes out of fs/nfs/nfs4recover.c, which is new to 14.1. It's this feature, I believe:
http://wiki.linux-nfs.org/wiki/index...erver_recovery
So, it looks like the kernel is looking for a user-space daemon to write a bit of state to disk, and is timing out. With the addition of such a feature to the kernel, it seems like Slackware should either disable V4 in the kernel or invest in supporting the required daemons. Hmm, that sounds a little too presumptuous. I guess I'll see what demons lie in turning on full V4 support...
|
|
|
02-24-2014, 02:55 AM
|
#7
|
Member
Registered: Apr 2009
Location: Oz
Distribution: slackware64-14.0
Posts: 875
|
The minimum required for nfs4 support is :-
remove
portmap
install
libevent
libnfsidmap
libtirpc
rpcbind
and recompile nfs-utils with nfs4 enabled
Sadly only libtirpc has a SlackBuild on slackbuilds.org
If you need additional encryption like kerberos have a look at this page :- http://canich.net/slackware/krb5.html
|
|
2 members found this post helpful.
|
02-24-2014, 04:30 PM
|
#8
|
Member
Registered: Aug 2006
Distribution: Slackware, OpenBSD, CentOS, Ubuntu
Posts: 99
Original Poster
Rep:
|
Thanks for the additional pointers. libevent is already in the base system, fyi.
|
|
|
All times are GMT -5. The time now is 08:08 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|