KShots
Guru
Joined: 09 Oct 2003
Posts: 503
Location: Florida
|
 Posted: Wed Feb 18, 2015 9:05 pm Post subject: NFS4 issues on upgrade |
 |
|
I recently performed an upgrade on my NFS server, and apparently I can no longer connect to it via NFS. Below is my exports: | Code: | /export/nfs4 fd4d:fefa:cc54::/48(sec=sys:krb5p,subtree_check,fsid=0)
/export/nfs4/home fd4d:fefa:cc54::/48(rw,sec=krb5p,no_subtree_check)
/export/nfs4/myth fd4d:fefa:cc54::/48(rw,no_subtree_check)
/export/nfs4/portage fd4d:fefa:cc54::/48(ro,no_subtree_check) |
Just so I'm not over-complicating things, let's focus on the "portage" mount, which does not invoke kerberos. When I attempt to manually mount it: | Code: | basilisk tmp # mount -vvvo ro,proto=tcp6 -t nfs4 gorgon:/portage tmp
mount.nfs4: timeout set for Wed Feb 18 15:50:19 2015
mount.nfs4: trying text-based options 'proto=tcp6,addr=fd4d:fefa:cc54:0:d250:99ff:fe3b:c46d,clientaddr=fd4d:fefa:cc54:0:62a4:4cff:feb3:82d5'
mount.nfs4: mount(2): Connection refused |
And yes, "gorgon" resolves to the addr= field above, which is the NFS server. Other interesting information from the client side: | Code: | basilisk tmp # rpcinfo -p gorgon
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 52042 status
100024 1 tcp 41989 status
100005 3 tcp 50639 mountd
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100021 1 udp 36201 nlockmgr
100021 3 udp 36201 nlockmgr
100021 4 udp 36201 nlockmgr
100021 1 tcp 45747 nlockmgr
100021 3 tcp 45747 nlockmgr
100021 4 tcp 45747 nlockmgr |
Somewhat telling: | Code: | gorgon ~ # netstat -l6 | grep nfs
gorgon ~ # netstat -l4 | grep nfs
netstat: no support for `AF INET (sctp)' on this system.
tcp 0 0 *:nfs *:* LISTEN |
This implies that, indeed, my NFS server is not listening (or, rather, it is only listen on IPv4 rather than IPv6). Any idea how I can convince it to listen on IPv6? I've tried using the '-H' option in rpc.nfsd, but it doesn't appear to recognize IPv6 addresses
[EDIT]
Ok, I've confirmed I can connect via IPv4 for the portage mount. I'd really prefer to mount via IPv6, though... anything I can do to make this work again, or is it broken in the current version?
_________________
Life without passion is death in disguise |
|
Networking & Security
