OpenVZ: Difference between /vz/private and /vz/root

[Sitemon]

What is the difference between /vz/private and /vz/root

I see that /vz/private/51 and /vz/root/51 are hard linked.
So now i want to move /vz/private/51 to dedicated filesystem how should I handle /vz/root/51?

Can i just symlink /vz/root/51 to /vz/private/51?

[Sitemon]

Got something helpful from google search:

/vz/private/<VEID> are private areas, i.e. the directories containing the private files of the given VEs.

/vz/root/<VEID> -- are mountpoints. The private area is mounted to the /vz/root/<VEID> directory on the Hardware Node and provides VE users with a complete Linux file system tree.


If you want to move VE files from HN to some other place it's better to avoid /vz/private using and handle /vz/root directory.

It's disk-quota related issue.

I would note that disk quota is calculated on /vz/private/<VEID> subtree. However it's able to track the operation only if VE is mounted. Quota is initialized on the first VE mount -- it is relative log procedure. When VE unmounts the collected quota information is saved to special file that reads again on the next VE start.

However if you have changed something inside private area where VE was unmounted, it makes inconsistent the quota information saved in file. Unfortunately we will know nothing about this fact and quota will show incorrect values when VE will be started again.

Thank you
It's disk-quota related issue.

I would note that disk quota is calculated on /vz/private/<VEID> subtree. However it's able to track the operation only if VE is mounted. Quota is initialized on the first VE mount -- it is relative log procedure. When VE unmounts the collected quota information is saved to special file that reads again on the next VE start.

However if you have changed something inside private area where VE was unmounted, it makes inconsistent the quota information saved in file. Unfortunately we will know nothing about this fact and quota will show incorrect values when VE will be started again.

Thank you,
Vasily Averin