Article ID: 121019, created on Apr 10, 2014, last review on May 11, 2014

  • Applies to:
  • Virtuozzo


A ploop container cannot be started or mounted:

[root@pcs ~]# vzctl --verbose mount 101
Mount image: /vz/private/101/~
Failed to mount image /vz/private/101/root.hdd: Can't add image /vz/private/101/root.hdd/root.hds: Device or resource busy
Failed to mount image: Can't add image /vz/private/101/root.hdd/root.hds: Device or resource busy [152]


The container is locked by a backup operation, which was never completed, i.e. abruptly interrupted. It resulted in a stuck ploop mount:

[root@pcs ~]# grep ploop /proc/mounts | grep backup
/dev/ploop28726p1 /vz/backup/101/tmpexH6Jq/fs ext4 ro,relatime,barrier=1,data=ordered,balloon_ino=12,pfcache_csum 0 0

The origin of the ploop locker can also be defined by looking into the following cookie file:

[root@pcs ~]# cat /sys/block/ploop28726/pstate/cookie


  • Unmount the hung mount:

    [root@pcs ~]# ploop umount -d /dev/ploop28726
    Unmounting file system at /vz/backup/101/tmpexH6Jq/fs
    Unmounting device /dev/ploop28726
  • Start the container:

    [root@pcs ~]# vzctl start 101

Search Words

can not mount ploop

0dd5b9380c7d4884d77587f3eb0fa8ef 2897d76d56d2010f4e3a28f864d69223

Email subscription for changes to this article
Save as PDF