On 25Aug2019 12:28, Bob Goodwin bobgoodwin@fastmail.us wrote:
On 8/23/19 7:07 PM, Cameron Simpson wrote:
Also, you can check from the client what a server is prepared to export to you: showmount -e 192.168.2.128
. [root@box6 bobg]# mount 192.168.2.128:/home /mnt/testb [root@box6 bobg]# showmount -e 192.168.2.128 Export list for 192.168.2.128: /home 192.168.2.0/24
Looks normal. .128 exports /home.
[bobg@box6 ~]$ ls -al /mnt/testb/bobg/ shows nothing that leads to /etc/exports, so my mount command is not right.
I don't understand what you expect here. /mnt/testb/bobg should show the contents of /home/bobg from the NFS server. Does it?
That is ... odd. The "mount" command should show you what is attached where on the client.
. mount shows: 192.168.2.128:/home on /mnt/testb type nfs4 (rw,relatime,vers=4.2,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.2.6,local_lock=none,addr=192.168.2.128) gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
Looks normal, matches what was in your "mount" command above.
and this is what I see in /etc/exports:
[bobg@NFS ~]$ cat /etc/exports /home 192.168.2.0/24(rw,no_root_squash)
Which looks normal: this exports /home to your subnet.
Where should the stored files be, it looks like I have it set up wrong?
Can you explain this sentence in more detail. Nothing above is weird looking from my point of view.
Cheers, Cameron Simpson cs@cskk.id.au