I’m running the NFS server on FreeNAS on top of VLAN tagged LACP interface. root@freenas:~ # cat /etc/exports V4: / -sec=sys /mnt/pool0/ovirt/he -network 192.168.10.0/29 /mnt/pool0/ovirt/vm -network 192.168.10.0/29 /mnt/pool0/ovirt/iso -network 192.168.10.0/29 Simple as this. On this hosts it gets mounted as this: 192.168.10.6:/mnt/pool0/ovirt/he on /rhev/data-center/mnt/192.168.10.6:_mnt_pool0_ovirt_he type nfs4 (rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,soft,nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,clientaddr=192.168.10.1,local_lock=none,addr=192.168.10.6) 192.168.10.6:/mnt/pool0/ovirt/vm on /rhev/data-center/mnt/192.168.10.6:_mnt_pool0_ovirt_vm type nfs4 (rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,soft,nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,clientaddr=192.168.10.1,local_lock=none,addr=192.168.10.6) 192.168.10.6:/mnt/pool0/ovirt/iso on /rhev/data-center/mnt/192.168.10.6:_mnt_pool0_ovirt_iso type nfs4 (rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,soft,nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,clientaddr=192.168.10.1,local_lock=none,addr=192.168.10.6)
On 12 Feb 2019, at 20:39, Nir Soffer <nsoffer@redhat.com> wrote:
Looking at https://bugzilla.redhat.com/1666795 <https://bugzilla.redhat.com/1666795>
It seems that a change in vdsm/libvirt exposed NFS configuration issue, that may was needed in the past and probably not needed now.
If you use NFS, I would like to see your /etc/exports (after sanitizing it if needed). For extra bonus, output of "exportfs -v" would be useful.
In particular, I want to know if you use root_squash, all_squash, or no_root_squash.
Thanks, Nir _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/7J3ZV25DP2X5TD...