11:12 p.m.
Storage domain usage is as follows：
vgdisplay 3542ca36-747b-407c-aa5e-331510f81fd9
--- Volume group ---
VG Name 3542ca36-747b-407c-aa5e-331510f81fd9
System ID
Format lvm2
Metadata Areas 2
Metadata Sequence No 15998
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1954
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size 113.97 TiB
PE Size 128.00 MiB
Total PE 933647
Alloc PE / Size 64930 / <7.93 TiB
Free PE / Size 868717 / 106.04 TiB
VG UUID GiL1LL-ggO5-a6mX-62uc-q597-B3X9-6bzC93
__________________________________________________________
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')",)
Excuse me, what's the reason, thank you!
11:38 p.m.
On April 27, 2020 6:12:08 AM GMT+03:00, liug74(a)sina.com wrote:
Storage domain usage is as follows：
vgdisplay 3542ca36-747b-407c-aa5e-331510f81fd9
--- Volume group ---
VG Name 3542ca36-747b-407c-aa5e-331510f81fd9
System ID
Format lvm2
Metadata Areas 2
Metadata Sequence No 15998
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1954
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size 113.97 TiB
PE Size 128.00 MiB
Total PE 933647
Alloc PE / Size 64930 / <7.93 TiB
Free PE / Size 868717 / 106.04 TiB
VG UUID GiL1LL-ggO5-a6mX-62uc-q597-B3X9-6bzC93
__________________________________________________________
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')",)
Excuse me, what's the reason, thank you!
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/5C76N3P4IAL...
If it wass a Gluster or NFS, I would mention inodes.
Yet, I'm not sure if oVirt uses an FS for block storage.
What is the UI showing for disk utilization ?
Best Regards,
Strahil Nikolov
5:52 p.m.
On Mon, Apr 27, 2020 at 6:13 AM <liug74(a)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
1698
days inactive
1700
days old
2 comments
3 participants
participants (3)
-
liug74＠sina.com -
Nir Soffer -
Strahil Nikolov