On Mon, Apr 27, 2020 at 6:13 AM <liug74@sina.com> wrote:
Storage domain usage is as follows： vgdisplay 3542ca36-747b-407c-aa5e-331510f81fd9
...
The following error occurred when I created the VM: VDSM H5 command HSMGetAllTasksStatusesVDS failed: Error creating a new volume: (u"Volume creation 62220be2-2781-4771-9373-84af5cc18f01 failed: (28, 'Sanlock resource write failure', 'No space left on device')",)
This error is not about storage space, but sanlock lockspace, the area where every host updates its liveliness. When activating a host, it takes 20-50 seconds until the hots joins the sanlock lockspace. During this time there is no lockspace so sanlock operations may fail with this error. After an unclean shutdown (e.g power loss) sanlock needs to wait more time to make sure no host is using the lockspace, so this state can last several minutes. oVirt engine monitors host lockspace status, and tries to avoid some operations in this state. We also try to wait few minutes until a lockspace is ready in other cases, so this error should not happen. If you are still experiencing this issue please file a bug and attach complete engine and vdsm logs from the time this issue started. Nir