ti did this and it almost works except the .mount file:
our hostname is fbc158 so,
set a link so .conf and .mount get to correct place:
restore the backup
I'm not sure what the 'tar: write error' was . i assume it is related to not being able to set execute mode on the .mount file, but I'll check into it further tomorrow by setting -v on the tar command ?
try to run it
but it will start without the .mount file
So next thing to figure out is how to set execute permission on the .mount :
or how are bind mounts done in 2.0 ?
our hostname is fbc158 so,
set a link so .conf and .mount get to correct place:
Code:
ln -s /etc/pve/nodes/fbc158/openvz /etc/vz/conf
restore the backup
Code:
root@fbc158 /var/lib/vz/fbc6bkp # vzrestore vzdump-openvz-101-2011_09_24-23_00_02.tar 3401
...tar: write error
INFO: restore openvz backup 'vzdump-openvz-101-2011_09_24-23_00_02.tar' successful
I'm not sure what the 'tar: write error' was . i assume it is related to not being able to set execute mode on the .mount file, but I'll check into it further tomorrow by setting -v on the tar command ?
try to run it
Code:
vzctl start 3401
Starting container ...
Initializing quota ...
Error exec /etc/pve/openvz/3401.mount: Permission denied
Error executing mount script /etc/pve/openvz/3401.mount
but it will start without the .mount file
Code:
mv 3401.mount 3401.mount-
vzctl start 3401
Starting container ...
Container is mounted
Adding IP address(es): 10.100.100.207
Setting CPU units: 50000
Setting CPUs: 4
Container start in progress..
So next thing to figure out is how to set execute permission on the .mount :
Code:
-rw-r----- 1 root www-data 365 Sep 30 22:51 3401.mount
root@fbc158 /etc/pve/nodes/fbc158/openvz # chmod +x 3401.mount
chmod: changing permissions of `3401.mount': Function not implemented
or how are bind mounts done in 2.0 ?
Last edited: