Failed to acquire lock: No space left on device error when trying to start Hosted Engine VM

Solution In Progress - Updated -

Issue

  • Hosted Engine is down and cannot be brought up on the hypervisors

  • The follow error is present in the hypervisor logs, but there is not a free space issue on the NFS share:

Jun 30 09:33:18 prh6evkvm001f01 vdsm vm.Vm ERROR vmId=`71e6a1b0-46f7-4ea6-9534-7eed6aa42fcd`::The vm start process failed#012Traceback (most recent call last):#012  File "/usr/share/vdsm/vm.py", line 2246, in _startUnderlyingVm#012    self._run()#012  File "/usr/share/vdsm/vm.py", line 3186, in _run#012    self._conne
ction.createXML(domxml, flags),#012  File "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", line 92, in wrapper#012    ret = f(*args, **kwargs)#012  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 2665, in createXML#012    if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=s
elf)#012libvirtError: Failed to acquire lock: No space left on device

Environment

  • Red Hat Enterprise Virtualization 3.3
  • Red Hat Enterprise Virtualization 3.4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.