Article ID: 114820, created on Sep 23, 2012, last review on May 6, 2014

  • Applies to:
  • Virtuozzo containers for Linux


After cloning a container with Parallels Plesk Panel installed the cloned container starts with the similar errors:
~# vzctl start 100;
Stopping Container ...
Container was stopped
Container is unmounted
Moving/copying CT#100 -> CT#1000000, [], [] ...
Check disk space
Syncing private area '/vz/private/100'->'/vz/private/1000000'
copy (using : [vzfsclone]) failed : Error: Can't write shortcut '/vz/private/1000000//root/opt/psa/handlers.default/before-remote/sender-domain/mydomain.tld/10-dd51-domainkeys-buPZxe': No such file or directory

Can't move/copy CT#100 -> CT#1000000, [], [] : copy (using : [vzfsclone]) failed : Error: Can't write shortcut '/vz/private/1000000//root/opt/psa/handlers.default/before-remote/sender-domain/mydomain.tld/10-dd51-domainkeys-buPZxe': No such file or directory


The issue of VZFS 3 incorrectly treating empty files with sticky bit is tracked under ID PCLIN-26649 and will be fixed in one of the Parallels Virtuozzo Containers updates.


Prior to cloning remove sticky bit from Parallels Plesk Panel main handler files:
chmod 0644 /vz/private/CTID/root/opt/psa/handlers/before-local/recipient/*/*

After cloning and successful startup re-build mail handlers inside the container:
/usr/local/psa/admin/sbin/mchk --with-spam

e8e50b42231236b82df27684e7ec0beb 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f

Email subscription for changes to this article
Save as PDF