P
punktea
Guest
First time posting! I've used PVE since 1.8 and I am really happy with performance and stability.
I've just finished installing a cluster of 3 nodes and I am testing "Migrate" function.
The container CT 171 is on NFS share and I migrate from server4c to server4a
Sep 13 17:18:35 starting migration of CT 171 to node 'server4a' (10.168.1.123)
Sep 13 17:18:35 container data is on shared storage 'server4c_export1'
Sep 13 17:18:35 dump 2nd level quota
Sep 13 17:18:35 initialize container on remote node 'server4a'
Sep 13 17:18:36 initializing remote quota
Sep 13 17:27:00 turn on remote quota
Sep 13 17:27:00 load 2nd level quota
Sep 13 17:27:00 turn off remote quota
Sep 13 17:27:00 start final cleanup
Sep 13 17:27:00 migration finished successfuly (duration 00:08:25)
TASK OK
It takes quite a while (8 minutes) to migrate and the bulk of time is spent doing "init quota"
ps -ef on destination server4a shows:
/usr/sbin/vzquota init 171 -b 8388608 -B 9227468 -i 1600000 -I 1760000 -p /mnt/pve/server4c_export1/private/171 -e 0 -n 0 -s 0
This process runs over NFS and can be quite slow
My question: if the image is on a shared storage, why is it necessary to init quota again ?
Is it possible to turn off initializing quota during migration ?
( I have tried 'vzquota off 171" but then migrate will fail and I had to fix it by running vzquote init 171 manually )
I've just finished installing a cluster of 3 nodes and I am testing "Migrate" function.
The container CT 171 is on NFS share and I migrate from server4c to server4a
Sep 13 17:18:35 starting migration of CT 171 to node 'server4a' (10.168.1.123)
Sep 13 17:18:35 container data is on shared storage 'server4c_export1'
Sep 13 17:18:35 dump 2nd level quota
Sep 13 17:18:35 initialize container on remote node 'server4a'
Sep 13 17:18:36 initializing remote quota
Sep 13 17:27:00 turn on remote quota
Sep 13 17:27:00 load 2nd level quota
Sep 13 17:27:00 turn off remote quota
Sep 13 17:27:00 start final cleanup
Sep 13 17:27:00 migration finished successfuly (duration 00:08:25)
TASK OK
It takes quite a while (8 minutes) to migrate and the bulk of time is spent doing "init quota"
ps -ef on destination server4a shows:
/usr/sbin/vzquota init 171 -b 8388608 -B 9227468 -i 1600000 -I 1760000 -p /mnt/pve/server4c_export1/private/171 -e 0 -n 0 -s 0
This process runs over NFS and can be quite slow
My question: if the image is on a shared storage, why is it necessary to init quota again ?
Is it possible to turn off initializing quota during migration ?
( I have tried 'vzquota off 171" but then migrate will fail and I had to fix it by running vzquote init 171 manually )