Hi everybody!
I've a problem creating new containers on Proxmox VE 2.0. Every time, I create a new container, I get this error message:
I've tried different templates and different settings for the disk space (between 4 GB and 80 GB which should be more than enough for the minimal system). The error keeps still the same:
The configuration is created (not checked if it is OK), but the private area only exists in a .tmp folder: /var/lib/vz/private/107.tmp instead of /var/lib/vz/private/107 in this case. If I rename the private folder to 107, I'm able to start the container. But what's with the quota? Was it set right? How to check?
My configuration is a two node cluster which already runs two containers (one newly created and one copied from an old PVE 1.9 host.) and a KVM guest. The container storages are local directories on each node. For ease, the NAS is currently not in use. The error message appears on creating containers on both nodes.
I only know the resource busy error in the vzquota context. But why can a local directory be temporary unavailable? Can anybody explain the error message to me and tell me how to fix it?
Regards
Christoph
I've a problem creating new containers on Proxmox VE 2.0. Every time, I create a new container, I get this error message:
Code:
Creating container private area (ubuntu-10.04-minimal_10.04_i386.tar.gz)
vzquota : (error) Quota off syscall for id 107: Resource temporarily unavailable
vzquota off failed [3]
vzquota : (warning) Quota is broken for id 107
Creation of container private area failed
TASK ERROR: command 'vzctl --skiplock create 107 --ostemplate /var/lib/vz/template/cache/ubuntu-10.04-minimal_10.04_i386.tar.gz --private /var/lib/vz/private/107' failed: exit code 66I've tried different templates and different settings for the disk space (between 4 GB and 80 GB which should be more than enough for the minimal system). The error keeps still the same:
Code:
vzquota : (error) Quota off syscall for id 107: Resource temporarily unavailableThe configuration is created (not checked if it is OK), but the private area only exists in a .tmp folder: /var/lib/vz/private/107.tmp instead of /var/lib/vz/private/107 in this case. If I rename the private folder to 107, I'm able to start the container. But what's with the quota? Was it set right? How to check?
My configuration is a two node cluster which already runs two containers (one newly created and one copied from an old PVE 1.9 host.) and a KVM guest. The container storages are local directories on each node. For ease, the NAS is currently not in use. The error message appears on creating containers on both nodes.
I only know the resource busy error in the vzquota context. But why can a local directory be temporary unavailable? Can anybody explain the error message to me and tell me how to fix it?
Regards
Christoph