| 1 |
On Monday, 23 December 2019 16:50:58 GMT Peter Humphrey wrote: |
| 2 |
> Hello list, |
| 3 |
> |
| 4 |
> Since I set up IPv6 on my LAN, I've been unable to NFS-export a directory on |
| 5 |
> machine A (an Atom serving portage via git, among other things) and mount |
| 6 |
> it on machine B (this workstation). It was working fine until then, but now |
| 7 |
> mount commands fail. In both kernels I have NFSv4 selected, but not 4.x; no |
| 8 |
> fancy extras like ACLs. |
| 9 |
> |
| 10 |
> I went back to the Gentoo nfs-utils wiki page and made sure I had everything |
| 11 |
> right, then searched for other people's problems. Nothing has helped so |
| 12 |
> far. |
| 13 |
> |
| 14 |
> On the server: |
| 15 |
> $ cat /etc/conf.d/nfs |
| 16 |
> NFS_NEEDED_SERVICES="rpc.idmapd" |
| 17 |
> OPTS_RPC_NFSD="1 -N 2 -N 3 -V 4 -N 4.1" |
| 18 |
> OPTS_RPC_MOUNTD="-p 32767" |
| 19 |
> OPTS_RPC_STATD="-p 32765 -o 32766" |
| 20 |
> OPTS_RPC_IDMAPD="" |
| 21 |
> OPTS_RPC_GSSD="" |
| 22 |
> OPTS_RPC_SVCGSSD="" |
| 23 |
> OPTS_RPC_RQUOTAD="" |
| 24 |
> EXPORTFS_TIMEOUT=30 |
| 25 |
> $ cat /etc/exports |
| 26 |
> mnt/nfs 192.168.1.5/24(rw,no_subtree_check,crossmnt,fsid=0) \ |
| 27 |
> fe80::5/64(rw,sync,no_subtree_check,crossmnt,fsid=0) |
| 28 |
> /mnt/nfs/portage |
| 29 |
> 192.168.1.5/24(rw,no_subtree_check,anonuid=250,anongid=250,fsid=1) \ |
| 30 |
> fe80::5/64(rw,no_subtree_check,anonuid=250,anongid=250,fsid=1) |
| 31 |
> /mnt/nfs/port.resc |
| 32 |
> 192.168.1.5/24(rw,no_subtree_check,anonuid=250,anongid=250,fsid=2) \ |
| 33 |
> fe80::5/64(rw,no_subtree_check,anonuid=250,anongid=250,fsid=2) $ grep nfs |
| 34 |
> /etc/fstab |
| 35 |
> /usr/portage /mnt/nfs/portage none bind |
| 36 |
> 0 0 |
| 37 |
> |
| 38 |
> On the client: |
| 39 |
> $ grep nfs /etc/fstab |
| 40 |
> 192.168.1.2:/mnt/nfs/portage /mnt/atom/usr/portage nfs4 |
| 41 |
> noauto,rw,_netdev 0 0 |
| 42 |
> |
| 43 |
> Now I try to mount /usr/portage from the host on /mnt/atom/usr/portage |
| 44 |
> (which does exist) and get this: |
| 45 |
> # mount /mnt/atom/usr/portage |
| 46 |
> mount.nfs4: mounting 192.168.1.2:/mnt/nfs/portage failed, reason given by |
| 47 |
> server: No such file or directory # mount 192.168.1.2:/mnt/nfs/portage |
| 48 |
> /mnt/atom/usr/portage |
| 49 |
> mount.nfs: mounting 192.168.1.2:/mnt/nfs/portage failed, reason given by |
| 50 |
> server: No such file or directory # mount [fe80::2]:/mnt/nfs/portage |
| 51 |
> /mnt/atom/usr/portage |
| 52 |
> mount.nfs: mount system call failed |
| 53 |
> |
| 54 |
> It doesn't seem to be a firewall problem, because I get the same result if I |
| 55 |
> start both machines without their firewalls - I don't do that very often! |
| 56 |
> Ping works fine in both directions, whether IPv4 or v6. Do I have to tweak |
| 57 |
> mapd somehow? |
| 58 |
> |
| 59 |
> I'm feeling a bit clueless... |
| 60 |
|
| 61 |
Is anyone feeling less clueless than me? I'm out of ideas now and hoping for |
| 62 |
some help. |
| 63 |
|
| 64 |
-- |
| 65 |
Regards, |
| 66 |
Peter. |
Archives