On Wed, Aug 1, 2018 at 3:02 PM Ed Greshko <ed.greshko(a)greshko.com> wrote:
On 08/01/18 19:37, Bob Goodwin wrote:
>
> [bobg@ASRock-J3455M ~]$ cat /etc/exports
> /home/exports
192.168.1.0/24(rw,sync,insecure,no_root_squash,no_subtree_check,fsid=0)
The problem with this line is "fsid=0".
Remove that (not sure what it is for) and it will work.
In nfsv4, there's a notion of a pseudo-filesystem whereby there's a
pseudo/virtual root filesystem.
So if you have
nfs_server # cat /etc/exports
/the/nfsv4/export/dir *(rw,fsid=0)
you have to mount this filesystem with
nfs_client # mount [ -o nfsvers=4 ] nfs_server:/ import_dir
but if you have
nfs_server # cat /etc/exports
/the/nfsv4/export/dir *(rw)
you have to mount this filesystem with
nfs_client # mount [ -o nfsvers=4 ] nfs_server:/the/nfsv4/export/dir import_dir
as you would with an nfsv3 server.
But because it's nfsv4, nfs_server's "/" has an fsid of 0 and
you'll
therefore be able mount any of "/" "/the" "/the/nfsv4"
"/the/nfsv4/export". They are exported as read-only and, even if you
mount "/", you wouldn't be able to access the usual directories under
"/", like "/usr".