Wow, thank you Gena! That clears things up. Now it's time to write a
check for open files and figure this out...
Thanks,
Chris
On 11/01/2016 05:11 PM, Gena Makhomed wrote:
On 01.11.2016 22:52, Chris James wrote:
It doesn't seem to do anything if the container is running:
It works with runn
On 01.11.2016 22:52, Chris James wrote:
It doesn't seem to do anything if the container is running:
It works with running containers too.
pcompact do nothing if threshold is not exceeded.
/etc/vz/pcompact.conf
# Start compacting if unused space is greater than specified THRESHOLD
in percen
Hi,
It doesn't seem to do anything if the container is running:
[root@sovereign ~]# du -sch /vz/private/101/root.hdd/
114G/vz/private/101/root.hdd/
[root@sovereign ~]# vzctl exec 101 df -h /
Filesystem Size Used Avail Use% Mounted on
/dev/ploop42957p1 277G 101G 162G 39% /
[root
On 03.10.2016 18:26, Chris James wrote:
I'm running a graphing container on VZ7. Specifically it's running
carbon-cache with metrics coming in every minute for a total of 46G of
stats spread out over 193349 files. This disk space usage of this
containers ploop container is regularly blowing up.
Hello Chris,
one way in which you could avoid that problem is to use simfs instead of ploop
for that container. Otherwise, yes, you should compact containers on a regular
basis (preferably during off peak hours...).
HTH
Best,
Corrado
___
> On 3 Oct 201
Howdy,
I'm running a graphing container on VZ7. Specifically it's running
carbon-cache with metrics coming in every minute for a total of 46G of
stats spread out over 193349 files. This disk space usage of this
containers ploop container is regularly blowing up.
Today, I ran the following command
