Re: autofs + default /net map + NFS4 — how to?

Rick Macklem rmacklem at uoguelph.ca
Thu May 13 22:24:44 UTC 2021


Lev wrote:
>On 14.05.2021 0:10, Rick Macklem wrote:
>
>> lev wrote:
>> [stuff snipped]
>>> I could mount "blob:/home" or "blob:/ports" with mount -t nfs like this:
>>>
>>> # mount -t nfs -o nfsv4,tcp blob:/home /mnt
>> Oh, and you might want to consider using "minorversion=1" (or even 2
>> if/when you are running FreeBSD13 or later).
>> NFSv4.1 (and 4.2) are much better protocols than NFSv4.0 and the
>> implementations should now be pretty solid, so long as you avoid
>> enabling delegations (off by default).
>
>  Could it be done on server-side? I don't want to touch all clients. Like "Prefer 4.2, but >allow 4.0 too"?
Not for the FreeBSD client. The Linux client uses the highest minor version supported
by both client and server unless the "minorversion" option is used to specify
what minor version is to be used.

When I first did NFSv4.1 I did not do this, because I considered in experimental.
Now, this would be nice to do, but I suspect it would be considered a POLA
violation.
--> Maybe I will ask on an email list to see if the "collective" thinks this is a
      good idea. In any case, this is not the case now.

>> - NFSv4.1 was a minor revision in name only. The RFC is only 500+ pages long.
>  "only"! :)
Yea. I still find things in the RFC that I did not know about.
Btw, 4.2 was a relatively minor change from 4.1, with all the new operations being
optional to implement. Things like "copy file range locally in the server",
SEEK_DATA/SEEK_HOLE that are optionally added to the server.

rick

--
// Lev Serebryakov


More information about the freebsd-fs mailing list