Create new disk failure

Re: oVirt and ARM

Image import to Managed Block...

Gangi Reddy

Friday, 9 July 2021 Fri, 9 Jul '21

1:28 p.m.

Software version: 4.4.6.7-1.el8 Error: VDSM server command HSMGetAllTasksStatusesVDS failed: value=Error creating a new volume: ("Volume creation 8f509d4b-6d37-44c5-aa37-acba17391143 failed: (28, 'Sanlock resource write failure', 'No space left on device')",) abortedcode=205

Show replies by date

Nir Soffer

Friday, 9 July Fri, 9 Jul

3:37 p.m.

On Fri, Jul 9, 2021 at 9:35 PM Gangi Reddy <gangireddy52(a)gmail.com> wrote:

...

This means the host did not join the lockspace yet, but this should be impossible on the SPM host, which is the only host that can create new volumes. The SPM host cannot become SPM without acquiring sanlock lease and this is not possible without having a lockspace. Please file ovirt bug for this with engine and vdsm log from the spm host. Trying the operation again is likely to succeed. If there was an issue with sanlock it is likely to be resolved automatically since the system is monitoring sanlock status and will recover from such issues automatically. Nir

Gangi Reddy

Monday, 12 July Mon, 12 Jul

10:59 a.m.

Thank you. Kindly share the Ovirt Node and VM max limits please. In terms of CPU/Memory/Storage. How many storage disks we can provision through one storage domain?