[ovirt-users] Re: error: "cannot set lock, no free lockspace" (localized)

2019-02-28 Thread Sahina Bose
Looking at the logs: In the vdsm log: 2019-02-26 17:07:09,440+0400 ERROR (check/loop) [storage.Monitor] Error checking path /rhev/data-center/mnt/glusterSD/ovirtnode1.miac:_vmstore/01f6fd06-9ad1-4957-bcda-df24dc4cc4f5/dom_md/metadata (monitor:498) Traceback (most recent call last): File

[ovirt-users] Re: error: "cannot set lock, no free lockspace" (localized)

2019-02-28 Thread Mike Lykov
01.03.2019 9:51, Sahina Bose пишет: > Any errors in vdsm.log or gluster mount log for this volume? > I cannot find any. Here is full logs from one node for that period: https://yadi.sk/d/BzLBb8VGNEwidw file name ovirtnode1-logs-260219.tar.gz gluster, vdsm logs for all volumes sanlock client

[ovirt-users] Re: error: "cannot set lock, no free lockspace" (localized)

2019-02-28 Thread Sahina Bose
Any errors in vdsm.log or gluster mount log for this volume? On Wed, Feb 27, 2019 at 1:07 PM Mike Lykov wrote: > > > Hi all. I have a HCI setup, glusterfs 3.12, ovirt 4.2.7, 4 nodes > > Yesterday I see 3 VMs detected by engine as "not responding" (it is marked as > HA VMs) > (it all located on