for RHEV, you can check the Cluster scheduling policiesThanks for the response.
As it turned out, the issue was on the export where I had to remove subtree_check and added no_root_squash and it started working.
Being new to the setup, I am still trying to work through some config issues and deciding if I want to continue. The main thing I am looking for is good HA and failover capability. Been using Proxmox VE and I like the admin of it, but failover still needs work. Simple things like auto migration when rebooting a host does not exist and is something I need.
_______________________________________________
Robert
From: Strahil Nikolov <hunter86_bg@yahoo.com>
Sent: Sunday, December 1, 2019 2:54 PM
To: users@ovirt.org <users@ovirt.org>; Robert Webb <rwebb@ropeguru.com>
Subject: Re: [ovirt-users] NFS Storage Domain on OpenMediaVaultDoes sanlock user has rights on the ...../dom_md/ids ?
Check the sanlock.service for issues.journalctl -u sanlock.service
Best Regards,Strahil Nikolov
В неделя, 1 декември 2019 г., 17:22:21 ч. Гринуич+2, rwebb@ropeguru.com <rwebb@ropeguru.com> написа:
I have a clean install with openmediavault as backend NFS and cannot get it to work. Keep getting permission errors even though I created a vdsm user and kvm group; and they are the owners of the directory on OMV with full permissions.
The directory gets created on the NFS side for the host, but then get the permission error and is removed form the host but the directory structure is left on the NFS server.
Logs:
From the engine:
Error while executing action New NFS Storage Domain: Unexpected exception
From the oVirt node log:
2019-11-29 10:03:02 136998 [30025]: open error -13 EACCES: no permission to open /rhev/data-center/mnt/192.168.1.56:_export_Datastore-oVirt/f38b19e4-8060-4467-860b-09cf606ccc15/dom_md/ids
2019-11-29 10:03:02 136998 [30025]: check that daemon user sanlock 179 group sanlock 179 has access to disk or file.
File system on Openmediavault:
drwxrwsrwx+ 3 vdsm kvm 4096 Nov 29 10:03 .
drwxr-xr-x 9 root root 4096 Nov 27 20:56 ..
drwxrwsr-x+ 4 vdsm kvm 4096 Nov 29 10:03 f38b19e4-8060-4467-860b-09cf606ccc15
drwxrwsr-x+ 4 vdsm kvm 4096 Nov 29 10:03 .
drwxrwsrwx+ 3 vdsm kvm 4096 Nov 29 10:03 ..
drwxrwsr-x+ 2 vdsm kvm 4096 Nov 29 10:03 dom_md
drwxrwsr-x+ 2 vdsm kvm 4096 Nov 29 10:03 images
drwxrwsr-x+ 2 vdsm kvm 4096 Nov 29 10:03 .
drwxrwsr-x+ 4 vdsm kvm 4096 Nov 29 10:03 ..
-rw-rw----+ 1 vdsm kvm 0 Nov 29 10:03 ids
-rw-rw----+ 1 vdsm kvm 16777216 Nov 29 10:03 inbox
-rw-rw----+ 1 vdsm kvm 0 Nov 29 10:03 leases
-rw-rw-r--+ 1 vdsm kvm 343 Nov 29 10:03 metadata
-rw-rw----+ 1 vdsm kvm 16777216 Nov 29 10:03 outbox
-rw-rw----+ 1 vdsm kvm 1302528 Nov 29 10:03 xleases
_______________________________________________
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/
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/KH2H2V254Z7T7GP6NK3TOVDQBAPRBLZS/