vzquota - Can't open quota file

B

benphelps

Guest
vzquota : (error) Can't open quota file for

vzquota : (error) Can't open quota file for id 110, maybe you need to reinitialize quota: No such file or directory

How can I fix this, the VPS will not start at all.

Code:
/usr/sbin/vzctl start 110
Starting container ...
Initializing quota ...
vzquota : (error) quota check : lstat `1MkK5K-0004Ws-2U-D': No such file or directory
vzquota init failed [1]
VM 110 start failed -
 
1. Stop the Virtual Machine / Container.
2. VM Manager -> Virtual Machines -> Click on the problem Container/VM line (110 line in your example - not on the red arrow but on the rest of the line)
3. Virtual machine Configuration -> Options -> check the Enable User Quotas checkbox.
4. Start the Virtual Machine / Container.
 
I turned quotas on and off a few times and it will not start. Will not start with quotas on or off.
 
I just tried to do this..

Code:
vpserv:~# vzquota drop  110 --force
vzquota : (error) Can't open quota file for id 110, maybe you need to reinitialize quota: No such file or directory

Where would this quota file be located at???

OpenVZ can't find it and it doesn't seem to want to even do anything if it can't find the file.
 
We've tried just about anything. Is there anyway for us to start that VPS without the quota file, or it must be present before it can be started?
 
While we figure out what exactly is going on, we're using the following temporary solution.

Add

DISK_QUOTA="no"

To

/etc/vz/conf/110.conf
 
We had a problem today on two openvz containers.

The error was quota related.

vzquota on failed [1]

Disabling through the webinterface did not work out.

So we added the line mentioned here.

DISK_QUOTA="no"

To

/etc/vz/conf/<vmid>.conf

And we were able to start both containers on this node.
Both containers seem to work fine but the diskspace
reads now 0 in the webinterface.


Is it safe to migrate both containers to another node while they
are in this 'state' or is rebuilding the quota on the two containers
first a better option?
 
We had a problem today on two openvz containers.

The error was quota related.

vzquota on failed [1]

Disabling through the webinterface did not work out.

So we added the line mentioned here.

DISK_QUOTA="no"

To

/etc/vz/conf/<vmid>.conf

And we were able to start both containers on this node.
Both containers seem to work fine but the diskspace
reads now 0 in the webinterface.


Is it safe to migrate both containers to another node while they
are in this 'state' or is rebuilding the quota on the two containers
first a better option?

And in addition, is it safe to do "vzquota init xxx" on an running container?

Thanks!
 
well aparently you can but:

node3:~# vzquota on 114
vzquota : (warning) Incorrect quota shutdown for id 114, recalculating disk usage
vzquota : (error) quota check : lstat `xinetd': No such file or directory

Some files are damaged I guess?
How do I solve this?
 
And in addition, is it safe to do "vzquota init xxx" on an running container?

I guess not.

Another question: Maybe you had opened a file inside the container private area from the host? Or an open container console?
 
Well not that I'm aware off (not exactly certain what it means).
But it is running.

Will it help if we migrate the container first with quota's off to try and enable them on the new server?
The server it is on now has problems with its filesystem.
 
I try to understand this quota stuff.
I run into this:

node2:/# vzquota on 139
vzquota : (error) Can't open quota file for id 139, maybe you need to reinitialize quota: No such file or directory

So I try:

node2:/# vzquota init 139
Usage: vzquota init <quotaid> -p <mount_path> [-c <quota_file>]
[-R,--relative]
[-s,--sub-quotas 1|0]
[-u,--ugid-limit <ugid_limit>]
-b,--block-softlimit <block_soft_limit>
-B,--block-hardlimit <block_hard_limit>
-i,--inode-softlimit <inode_soft_limit>
-I,--inode-hardlimit <inode_hard_limit>
-e,--block-exptime <block_expiration_time>
-n,--inode-exptime <inode_expiration_time>

"vzquota init xxx" is supposed to work?
I solved it by manually editing the config file setting quota to yes, but I can't imagine that this is the proper way?
 
had the same problem tried various things before just putting disk_quota=no in the config

tell me i have this problem, only when i chane /etc/vz/conf/xxx.conf with disk_qouta="no" all it's ok but the disk is 0, how i can fix this problem, i need disk quota on but i can't pls very thanks
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!