On Thu, Aug 2, 2018 at 12:29 AM Ed Greshko <ed.greshko(a)greshko.com> wrote:
On 08/01/18 23:22, Bob Goodwin wrote:
> On 08/01/18 08:38, Ed Greshko wrote:
>> On 08/01/18 20:17, Ed Greshko wrote:
>>> On 08/01/18 19:37, Bob Goodwin wrote:
>>>> On 08/01/18 07:31, Ed Greshko wrote:
>>>>> ll /etc/exports
>>>> Sorry, guess I wasn't completely awake at the time ...
>>>>
>>>> [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.
>>
>> OK, I looked up what "fsid=0" is all about. Now it is clear why that
fails.
>>
>> Read here for a complete understanding.
>>
>>
https://www.centos.org/docs/5/html/Deployment_Guide-en-US/s1-nfs-server-c...
>>
>> Section 18.7.1.1. I had used that setup in the past, but forgot all
>> about it.
>
> Is that saying the client fstab instruction would have to be written
> differently?
>
> I read that a number of times and am still confused. Was removing
> fsid- just the simpler than changing the client side?
I think TomH laid it out quite well.
Bottom line, best not configure the server for a feature you're not
using or is confusing. :-)
I suspect that the reason for "fsid=0" is that, in the early day of
nfsv4 on linux, if you didn't specify it, it would be the highest
level share that would be the pseudo-filesystem's root, not "/".