OpenVZ error: container disk over quota of 295% in a week...

[BiagioParuolo]

Hi,

I've a container that goes over quota of 295% in a week...from 17Gb to 60Gb ...
I don't know why!!! and where found that eat space....
Help..?! How return to 17Gb...
If I made "rm *" in a dir I've error argument list too long!!!

 

[mmenaz]

I've a similar problem with an installation in Proxmox 1.3, Zimbra inside. Times to time /opt/zimbra/log fills the space.
If you want to know which dir occupies most space you can run something like:

# du -s ./* | sort -n | cut -f 2- | xargs -i du -sh {}

and see wich one is too big.
If is a dir you can remove, use:

# rm -r dirname

because "rm *" expands the "*" in a file names list, that could be too big for your environment.
Usually after freed some space, stopping and re-running the OpenVZ VM fixes the occupation info.
If is not the case, you should:

# vzctl stop <vmid>
# vzquota drop <vmid>
# vzctl start <vmid>

You should investigate if is a container error, or maybe you'd better upgrade to latest Proxmox 1.7 in the hope it fixes the problem.

N.B. "#" at the beginning of the line means you have to run this command as root
<vmid> means the numeric ID of your VM, i.e. 102 (so, i.e., you run vzctl stop 102 as root)

 

[BiagioParuolo]

Thank you...
Problem was the amavis tmp dir......It grow up , in a week over 50gb....why?