On 03/12/2018 10:09 PM, Carlos E. R. wrote:
On Monday, 2018-03-12 at 11:06 +0300, Andrei Borzenkov wrote:
Not for NFSv4. In NFSv4 design all exported resources belong to a single (virtual) tree. So this is actually correct - as long as you can drill down and see nested resources.
And Carlos tried to mount using NFSv4. Of course he did not explain whether "copied fstab entries" were using NFSv3 or not, so we have no idea if this is the reason for this problem.
192.168.1.14:/data/storage_c/repositorios_zypp/ /data/data_nfs_tc nfs4 defaults,rw,noauto,_netdev,nfsvers=4 0 0
This line worked instantly. I simply copied the line across from working 42.3 install.
And I doubt the original line was fully generated by yast2-nfs-client without some user intervention to refine the mount options. That line contains "nfsvers=4" which is the right and correct way of specifying the version nowadays. Unfortunately, yast2-nfs-client in 42.3 still used the legacy way, which is specifying "nfs4" in the vfstype column and no particular mount option. That is still not corrected in Leap15. So it behaves exactly the same than 42.3. So you should do exactly what you did in 42.3 - specifying the directory "by hand" (not trusting NFSv4 autodiscovery) and improving the mount options also by hand. No chance yast2-nfs-client in 42.3 generated that line automatically without the user helping it a bit. Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org