nvazquez commented on issue #5491: URL: https://github.com/apache/cloudstack/issues/5491#issuecomment-1016016243
Great to know @Hudratronium, in my setup the mount command works without specifying a version, however it picks up version 4.2 as the default version and the command succeeds ```` # mount -v 192.168.1.9:/export/secondary/template/tmpl/7/208 /test/ -o nodev,nosuid,noexec mount.nfs: timeout set for Tue Jan 18 22:52:39 2022 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.9,clientaddr=192.168.1.10' ```` Also tried with the specific version 4.1 and also succeeds: ```` # mount -v 192.168.1.9:/export/secondary/template/tmpl/7/208 /test/ -o nodev,nosuid,noexec,vers=4.1 mount.nfs: timeout set for Tue Jan 18 23:18:33 2022 mount.nfs: trying text-based options 'vers=4.1,addr=192.168.1.9,clientaddr=192.168.1.10' # mount | grep 208 192.168.1.9:/export/secondary/template/tmpl/7/208 on /test type nfs4 (rw,nosuid,nodev,noexec,relatime,vers=4.1,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.10,local_lock=none,addr=192.168.1.9) ```` One additional question: the original issue was reported on 4.15.2, is your NFS server now running properly on the same CloudStack version or have upgraded it to 4.16.0? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
