On 07/22/2015 01:08 PM, Gena Makhomed wrote: > > My experience with ploop: > > DISKSPACE limited to 256 GiB, real data used inside container > was near 40-50% of limit 256 GiB, but ploop image is lot bigger, > it use near 256 GiB of space at hardware node. Overhead ~ 50-60% > > I found workaround for this: run "/usr/sbin/vzctl compact $CT" > via cron every night, and now ploop image has less overhead. > > current state: > > on hardware node: > > # du -b /vz/private/155/root.hdd > 205963399961 /vz/private/155/root.hdd > > inside container: > > # df -B1 > Filesystem 1B-blocks Used Available Use% > Mounted on > /dev/ploop38149p1 270426705920 163129053184 94928560128 64% / >
Suprised about 256GiB limitation, (ext4+Ploop)
on my side (one of many container)
#ls -lh
total 461G
-rw-r--r-- 1 root root 796 Jul 22 13:45 DiskDescriptor.xml
-rw------- 1 root root 0 Dec 29 2014 DiskDescriptor.xml.lck
-rw------- 1 root root 461G Jul 19 04:56 root.hdd
From inside the container
#df -h
filesystem 1K-blocks Used Available Use% Mounted on
/dev/ploop21016p1 493G 382G 86G 82% /
So I am above 265GiB limit, what am I missing?
I agree with Kir, seen a huge difference in performance
going from simfs to ploop.
Same activity, HOST load was skyrocketing easily above mark 20,
while now load is kept within mark 5.
I was reluctant to move to ploop at first, moved away
from simfs January 2015, no regret at all.
Many thanks for all Kir.
--
A bientôt
===========================================================
Jean-Marc Pigeon E-Mail: j...@safe.ca
SAFE Inc. Phone: (514) 493-4280
Clement, 'a kiss solution' to get rid of SPAM (at last)
Clement' Home base <"http://www.clement.safe.ca";>
===========================================================
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
