Trying to improve our partitions and mount points while migrating a new server to the latest release we are splitting some partitions in order to improve mount points with specific parameters (as noatime,data=writeback,barrier=0,nobh and others) for web files, mysql, etc
We currently only use OpenVZ containers that share data partitions via bind mounts from the host. This is a data dir is mounted from the hosts /data/xxxx dir. That /data partition has the specific parameters assigned.
I am uncertain if:
Also posted at Stackoverflow - http://stackoverflow.com/q/14734002/169801
thanks
We currently only use OpenVZ containers that share data partitions via bind mounts from the host. This is a data dir is mounted from the hosts /data/xxxx dir. That /data partition has the specific parameters assigned.
I am uncertain if:
- bind mounts on containers inherit whatever mounting specifications of this type or need to be reassigned on the VIDXXX.mount file?
- I am aware there is a vzctl param to force it via command line... "vzctl set veid --noatime yes --save" but are there any other form (via conf files) to include the "noatime" or other mount options for the VM root itself, or they would be inherited also from the /var/lib/vz/ mount options. Would I need in that case to include them also in the bind mounts?
- are there are any issues as far as PVE itself if the system root partition includes params such as noatime?
Also posted at Stackoverflow - http://stackoverflow.com/q/14734002/169801
thanks
Last edited: