You are not logged in.
Just upgraded to NFSv4
# pacman -Qi nfs-utils
Name : nfs-utils
Version : 1.2.0-3
...# pacman -Qi kernel26
Name : kernel26
Version : 2.6.30-5
...
Same on both the server and client.
When I try to NFS mount from the client, I get this error:
# mount -t nfs4 vendhya:/vcpp /var/cache/pacman/pkg
mount.nfs4: No such device
I've tried manually loading the nfs4 module:
# grep nfs /proc/filesystems
nodev nfs
nodev nfs4
# lsmod | grep nfs
nfs 295280 0
lockd 72876 1 nfs
fscache 44688 1 nfs
nfs_acl 2884 1 nfs
auth_rpcgss 38144 1 nfs
sunrpc 190560 4 nfs,lockd,nfs_acl,auth_rpcgss
# modprobe nfs4
FATAL: Module nfs4 not found.
Anyone else encountered this?
Last edited by Painless (2009-06-24 08:36:50)
Offline
Sorry, found a typo in /etc/conf.d/nfs-common. It works now.
Offline
I'm getting similar issues to this, what did you have to change in nfs-common???
Offline
Hi Brenix,
I run NFS through a firewall, so I use fixed ports for statd (which I'm only using for a little while 'til everything gets moved over to NFS4). The firewall also requires that smnotify has it's port fixed.
NEED_STATD=
STATD_OPTS="-p 12345 -o 12346"
SMNOTIFY_OPTS="-p 12344"
NEED_IDMAPD=yes
IDMAPD_OPTS=
NEED_GSSD=no
GSSD_OPTS=
PIPEFS_MOUNTPOINT=
PIPEFS_MOUNTOPTS=
(Basically, it needs to be identical to the /etc/conf.d/nfs-common.conf on your server.)
I got some issues when not specifying NFS4 as the filesystem type. I found I had to use:
mount -t nfs4 server:/remote_mountpoint /local/mountpoint
Also, I used to disable autoload of the ipv6 module. This seems to be required by NFS4, so you may need to modprobe ipv6 on both client and server.
Finally, I didn't need the rpc_pipefs entry mentioned in the wiki in /etc/fstab for the client or the server.
Hope this helps!
Offline