| 1 |
On Tuesday, 10 March 2020 08:17:41 GMT netfab wrote: |
| 2 |
> Le 09/03/20 à 17:03, Peter Humphrey a tapoté : |
| 3 |
> > mount -t nfs 192.168.1.4:/mnt/nfs/portage /mnt/clrn/usr/portage # |
| 4 |
> > script on the client |
| 5 |
> > |
| 6 |
> > Result: |
| 7 |
> > * Mounting chroot dirs under /mnt/clrn ... |
| 8 |
> > mount.nfs: mounting 192.168.1.4:/mnt/nfs/portage failed, reason given |
| 9 |
> > by server: No such file or directory |
| 10 |
> |
| 11 |
> [...] |
| 12 |
> |
| 13 |
> > Can anyone see the problem? |
| 14 |
> |
| 15 |
> From the client, please try this : |
| 16 |
> > # mkdir /mnt/nfs4 |
| 17 |
> > # mount -t nfs4 192.168.1.4:/ /mnt/nfs4 |
| 18 |
> > # ls /mnt/nfs4 |
| 19 |
|
| 20 |
According to the following wiki page, with NFSv4 when mounting NFS from the |
| 21 |
client you use relative paths to the virtual root on the server. |
| 22 |
|
| 23 |
https://wiki.gentoo.org/wiki/Nfs-utils |
| 24 |
|
| 25 |
Therefore I also think the syntax netfab suggests above is how you should try |
| 26 |
it in the first instance; e.g.: |
| 27 |
|
| 28 |
mount -t nfs 192.168.1.4:portage /mnt/clrn/usr/portage |
| 29 |
|
| 30 |
or |
| 31 |
|
| 32 |
mount -t nfs 192.168.1.4:/portage /mnt/clrn/usr/portage |
Archives