Mauro, Have you seen this doc entry: https://docs.cloudstack.apache.org/en/latest/adminguide/storage.html#setting-nfs-mount-options-on-the-storage-pool It explains how you can set nfs options in version 4.19.1++ It sound like your solution is there.
On Wed, Nov 13, 2024 at 2:47 PM Mauro Ferraro - G2K Hosting < mferr...@g2khosting.com> wrote: > Good morning guys, > > We have a situation about CS and NFS, we are trying to make some > customizations with CS 4.17 parameters when mounting NFS server from > hosts with version 4 and we can see that this feature is working on > 4.19.1, so, we make a lab with 4.17 and upgrade it to 4.19.1. > > When we do this, see that CS 4.19.1 changes the type option in the mount > command and mount the resources in nfs3 for default, this is very > serious altough is a lab so we continue with the tests. > > */Mounted command with CS 4.17 (working) > /* > > /10.0.10.102:/cloudstack on /mnt/4c524bab-25a3-3db5-a665-d37159b81f11 > *type nfs4 > > *(rw,nosuid,nodev,noexec,relatime,*vers=4.2*,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.0.10.33,local_lock=none,addr=10.0.10.102)/ > > */Mounted command with CS 4.19.1 (working but nfs3) > /* > > /10.0.10.104:/cloudstack on /mnt/1a5453f8-0ddc-395c-bafc-1e196b4e7269 > *type nfs* > > (rw,nosuid,nodev,noexec,relatime,*vers=3*,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.0.10.104,mountvers=3,mountport=51219,mountproto=udp,local_lock=none,addr=10.0.10.104)/ > > Then we try to force nfs version to 4 wth the parameters that suggest in > the web > ( > https://docs.cloudstack.apache.org/en/4.19.1.0/adminguide/storage.html#storage-tags) > > and doesn't work. > > /2024-11-13 09:32:52,703 ERROR [kvm.storage.LibvirtStorageAdaptor] > (agentRequest-Handler-4:null) (logid:cd3c3be8) > org.libvirt.LibvirtException: internal error: Child process (/bin/mount > 10.0.10.104:/cloudstack /mnt/1a5453f8-0ddc-395c-bafc-1e196b4e7269 -o > nodev,nosuid,noexec,*vers=4.2*,nconnect=8) unexpected exit status 32: > mount.nfs: mounting 10.0.10.104:/cloudstack failed, reason given by > server: No such file or directory/ > > > The nfs server is the same with same configuration in the 3 tests, so we > can't understand the failure. Can you help us with this?- > > Regards, > > > > > > > > > > -- Daan
