On Tue, Aug 4, 2020 at 10:02 PM Arden Shackelford <zuntaruk@librem.one> wrote:
Hey Amit,
Thanks for the response. Here's what I've got:
Are your NFS exports permissions set correctly (probably yes if you can see something created on your share)?
Here's the perms on the folder (/mnt/ovirt on NFS server):
File: ovirt Size: 2 Blocks: 1 IO Block: 512 directory Device: 33h/51d Inode: 34 Links: 2 Access: (0755/drwxr-xr-x) Uid: ( 36/ vdsm) Gid: ( 36/kvmovirt) Access: 2020-08-04 17:54:06.971018988 +0000 Modify: 2020-08-04 17:54:09.410982092 +0000 Change: 2020-08-04 17:54:09.410982092 +0000 Birth: -
Can you list your share contents with ls -lhZ?
Root of share:
drwxrwxr-x 4 vdsm kvmovirt ? 4 Aug 4 18:52 c6244268-aaeb-4b67-b12b-8a0e81d7c205
I think selinux is not supported on your file system. Here is a working setup: On the host: # ls -lhZ /rhev/data-center/mnt/nfs1\:_export_1/ total 0 drwxr-xr-x. 5 vdsm kvm system_u:object_r:nfs_t:s0 48 Jun 20 03:56 56ecc03c-4bb5-4792-8971-3c51ea924d2e On the server: # ls -lhZ /export/1 total 0 drwxr-xr-x. 5 vdsm kvm system_u:object_r:unlabeled_t:s0 48 Jun 20 03:56 56ecc03c-4bb5-4792-8971-3c51ea924d2e
Inside of that:
drwxrwxr-x 2 vdsm kvmovirt ? 8 Aug 4 18:52 dom_md drwxrwxr-x 2 vdsm kvmovirt ? 2 Aug 4 18:52 images
Can you share the full error trace from vdsm.log?
Here's what I see: ... 2020-08-04 13:52:58,819-0500 ERROR (jsonrpc/1) [storage.initSANLock] Cannot initialize SANLock for domain c6244268-aaeb-4b67-b12b-8a0e81d7c205 (clusterlock:259) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/clusterlock.py", line 250, in initSANLock lockspace_name, idsPath, align=alignment, sector=block_size) sanlock.SanlockException: (19, 'Sanlock lockspace write failure', 'No such device')
I think this is this bug: https://bugzilla.redhat.com/1778485 Sanlok gets EACCESS - probably because selinux is disabled on the server, or not supported with ZFS, and then it returns ENODEV. Unfortunately this was not fixed yet in sanlock. To fix this, try to get selinux working on your server, or use another filesystem instead of ZFS. ZFS is not tested with oVirt, so while it may have great features, you may have even more trouble later even if you can get it working. Nir