Article ID: 119935, created on Jan 31, 2014, last review on May 11, 2014

  • Applies to:
  • Virtuozzo 6.0


A ploop container cannot be mounted with the following errors:

[root@pcs ~]# vzctl mount 101
Mount image: /vz/private/101/root.hdd
Failed to mount image /vz/private/101/root.hdd: /vz/private/101/root.hdd/root.hds.{356f5cdb-3465-47f0-89fa-c37603b605c0} (ro): irrecoverable errors
Failed to mount image: /vz/private/101/root.hdd/root.hds.{356f5cdb-3465-47f0-89fa-c37603b605c0} (ro): irrecoverable errors [152]

Checking all its images for consistency reveals a sparse .hds file:

[root@pcs ~]# ploop-check -dfc /vz/private/101/root.hdd/root.hds.\{356f5cdb-3465-47f0-89fa-c37603b605c0\}
Dirty flag is set
Delta files /vz/private/101/root.hdd/root.hds.{356f5cdb-3465-47f0-89fa-c37603b605c0} contains uninitialized blocks (offset=695663067136 len=12288) which are not aligned to cluster size
Error: ploop image '/vz/private/101/root.hdd/root.hds.{356f5cdb-3465-47f0-89fa-c37603b605c0}' is sparse.


The issue is recognized as a PCS product bug with internal ID PSBM-24694. Sometimes ploop images may get corrupted under low disk space condition on the hardware node.


Run ploop-check with "-S" option on the sparse snapshot:

# ploop-check -dfcS root.hds.\{356f5cdb-3465-47f0-89fa-c37603b605c0\}

After that, mount and unmount the container with ploop utility:

# ploop mount /vz/private/101/root.hdd/DiskDescriptor.xml
# ploop umount /vz/private/101/root.hdd/DiskDescriptor.xml

It should be possible to mount and start the container afterwards.

Search Words

irrecoverable errors

c62e8726973f80975db0531f1ed5c6a2 2897d76d56d2010f4e3a28f864d69223 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF