On Tue, Jan 19, 2021 at 3:43 PM Yedidyah Bar David <didi(a)redhat.com> wrote:
...
> 2021-01-18 08:43:25,524-0700 INFO (jsonrpc/0) [storage.SANLock]
Initializing sanlock for domain 4b3fb9a9-6975-4b80-a2c1-af4e30865088
path=/rhev/data-center/mnt/stumpy:_tanker_ovirt_host__storage/4b3fb9a9-6975-4b80-a2c1-af4e30865088/dom_md/ids
alignment=1048576 block_size=512 io_timeout=10 (clusterlock:286)
> 2021-01-18 08:43:25,533-0700 ERROR (jsonrpc/0) [storage.SANLock] Cannot initialize
lock for domain 4b3fb9a9-6975-4b80-a2c1-af4e30865088 (clusterlock:305)
> Traceback (most recent call last):
> File "/usr/lib/python3.6/site-packages/vdsm/storage/clusterlock.py",
line 295, in initLock
> sector=self._block_size)
> sanlock.SanlockException: (19, 'Sanlock lockspace write failure', 'No
such device')
> 2021-01-18 08:43:25,534-0700 INFO (jsonrpc/0) [vdsm.api] FINISH createStorageDomain
error=Could not initialize cluster lock: () from=::ffff:192.168.222.53,39612,
flow_id=5618fb28, task_id=49a1bc04-91d0-4d8f-b847-b6461d980495 (api:52)
> 2021-01-18 08:43:25,534-0700 ERROR (jsonrpc/0) [storage.TaskManager.Task]
(Task='49a1bc04-91d0-4d8f-b847-b6461d980495') Unexpected error (task:880)
> Traceback (most recent call last):
> File "/usr/lib/python3.6/site-packages/vdsm/storage/clusterlock.py",
line 295, in initLock
> sector=self._block_size)
> sanlock.SanlockException: (19, 'Sanlock lockspace write failure', 'No
such device')
I think this ^^ is the issue. Can you please check /var/log/sanlock.log?
This is a symptom of inaccessible storage. Sanlock failed to write to
the "ids" file.
We need to understand why sanlock failed. If the partialy created domain is
still available, this may explain the issue:
ls -lhZ /rhv/data-center/mnt/server:_path/storage-domain-uuid/dom_md
ps -efz | grep sanlock
ausearch -m avc
Nir