On Wed, 02 Apr 2025, mvogt1@xxxxxxxxx wrote:
> Hello,
>
>
> I have a netapp NFS server, from which I need to mount the NFS export
> with the client option:
> vers=4.1.
>
> The reason is, that the server exports 4.2, but this has some issue
> with SSC therefore we need to downgrade the client, which uses
> userspace copy in 4.1
>
> For example, the fs5 export should be mounted like this:
>
> fs5.domain.de:/vol/fs5_m_scratch on /m/scratch/space type nfs4
> (rw,nosuid,nodev,relatime,vers=4.1,rsize=65536,wsize=65536,..)
>
> My idea was to use ("man nfsmount.conf")
>
> [root@v110it01 nfsmount.conf.d]# pwd
> /etc/nfsmount.conf.d
> [root@v110it01 nfsmount.conf.d]# cat netapp.conf
>
>
> [ NFSMount_Global_Options ]
> Defaultvers=4.2
>
> [ Server "fs5.domain.de" ]
> rsize=32768
> vers=4.1
>
> [ Server "fs6.domain.de" ]
> vers=4.1
>
>
> This does not work, it uses vers=4.2.
> The only thing which seems to work reliably is to use the
> NFSMount_Global_Options.
> If it works, I can reverse the entries and then it does not work anymore.
> This is a bit strange, but its harder to reproduce a working mount,
> than a non working.
>
> I monitor the mount with and then edit the file in another terminal
>
> while true ; do
>
> mount fs5.domain.de:/vol/fs5_m_scratch /mnt/
> mount | grep /mnt
> sleep 4
> umount /mnt
> sleep 1
> done
>
> If I add rsize, for fs5 this is used, but not the vers=4.1.
> If I change the name from fs6 to fs5 and have two fs5 entries it works too,
> as soon I change it back to fs6 the mount is vers=4.2.
>
> This is verified for :
>
> - nfs-utils-2.5.4-27.el9.x86_64 (el9)
> - bookworm (debian)
>
> best regards,
This bug was fixed upstream just a few months ago:
Commit 307a75f56b56 ("conffile: add 'arg' argument to conf_remove_now()")
The fix will be in 2.8.3 which is not yet released.
If you ask your vendor nicely they might include the fix in an update,
or you could build from source yourself...
NeilBrown
