Editing Vzmigrate filesystem aware
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 2: | Line 2: | ||
Reading thoroughly quick installation documentation, it says "It is recommended to use a separate partition for container's private directories (by default /vz/private/<veid>)". As much as I searched the net, I have not found anything about it. | Reading thoroughly quick installation documentation, it says "It is recommended to use a separate partition for container's private directories (by default /vz/private/<veid>)". As much as I searched the net, I have not found anything about it. | ||
− | This is | + | This is a subject a thought about long ago, but I considered difficult to do in current |
− | implementation. Now things | + | implementation. Now things had changed. I have received directives in my job to have each container in separated filesystems insulated from the rest of containers. |
− | Actually vzmigrate does not | + | Actually vzmigrate does not have into account this issue. vzmigrate assume data are available when migration occurs and it does not know about filesystems neither mounted filesystems at all. |
Because of this matters, this issue I had put in his moment off until new order has got back to the scene. | Because of this matters, this issue I had put in his moment off until new order has got back to the scene. |