SlackwareThis 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.
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.
NAME
nfs - fstab format and options for the nfs and nfs4 file systems
SYNOPSIS
/etc/fstab
DESCRIPTION
NFS is an Internet Standard protocol created by Sun Microsystems in
1984. NFS was developed to allow file sharing between systems residing
on a local area network. The Linux NFS client supports three versions
of the NFS protocol: NFS version 2 [RFC1094], NFS version 3 [RFC1813],
and NFS version 4 [RFC3530].
I believe that the support is contained/supported by '/sbin/mount.nfs'. You could try the 'auto' to see if it works. You are certain that it is a nfs4 filesystem?
Yes, I'm sure.. I mounted the same filesystem on a Debian box using mount -t nfs4 and /bin/mount showed me:
Code:
10.0.0.17:/data on /mnt/data type nfs4 (rw,addr=10.0.0.17)
When I try from my Slackware box with mount -t auto, it tells me:
Code:
mount: special device 10.0.0.17:/data does not exist
When I try with mount -t nfs I get access denied and the server log complains:
Code:
May 25 19:31:05 s17 mountd[3869]: refused mount request from 10.0.0.26 for /data (/): not exported
mountd shouldn't even be involved in an nfs4 mount, right? So mount -t nfs probably tried to use v3 instead, and failed.
EDIT:
Looked at my kernel config, it seems the default is:
Code:
# CONFIG_NFS_V4 is not set
CONFIG_NFSD_V4=y
Kind of strange that the default has v4 server enabled, but not client, but okay.. on the off chance, I recompiled my kernel with CONFIG_NFS_V4=y, and also reinstalled the nfs-utils package, but neither made any difference.
For reference, and in case nfs4 support doesn't make it into the next Slackware, here's how to add your own, quick and dirty:
Download, configure && make && make install libevent and libnfsidmap, find them at citi
Grab the nfs-utils slackbuild and sources from your favorite mirror. Edit the slackbuild, s/--enable-nfsv4=no/--enable-nfsv4/g, comment out line 103 (rm -rf $PKG/sbin/*nfs4), build and install the nfs-utils package
Recompile your kernel with CONFIG_NFS_V4=y
modprobe nfs, this doesn't get autoloaded for some reason
mount -t nfs4 your.nfs4.server:/path /mnt/point (if you don't specify -t, mount will try nfsv3 instead)
Tried to mount an NFSv4 export from a HPC server so I could ramp up openmpi on multiple boxen.
mount.nfs: an incorrect mount option was specified
Checking the SlackBuild configure, "--enable-nfsv4=no" is still in Slackware Current (nfs-utils-1.2.3-x86_64-3). This after spending some time trying to figure out why the directory /var/lib/nfs/v4recovery was missing. If I ssh to the cluster, I can mount /home/hpc1, mpirun appears to work, but I'm rewriting the cpu/core inventory to include the cpuid info (the processes could all be running on the 4 cores on that box). Farther down in nfs-utils.SlackBuild:
# No NFSv4 yet, so remove these:
rm -f $PKG/sbin/*nfs4
provides another clue. Which libraries are missing? I'll try to configure and make the source with nfs4 enabled, maybe ldd will say what's missing?
I know the Slackware Team has their plate full, so we need to pitch in and help in such matters. Current file list has 3148 packages to manage.
`bzcat MANIFEST.bz2 | wc -l` is up to 376,576 files, not that anyone installs everything.
checking for krb5_get_error_message in -lgssapi_krb5... yes
checking for krb5_get_init_creds_opt_set_addressless in -lgssapi_krb5... no
checking for authgss_create_default in -lrpcsecgss... no
configure: error: librpcsecgss not found.
make: *** Nessun obiettivo specificato e nessun makefile trovato. Stop.
make: *** Nessun obiettivo specificato e nessun makefile trovato. Stop.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.