Hi Joe,
Am 08.04.2012 00:48, schrieb jjs - mainphrame:
Thanks for the pointer to the article, that's good info. I've checked
my system, and I'm nowhere near the limit of space or inodes.
To further test, I create a ploop CT which contains the expected
amount of disk space.
I then create a simfs CT with the same disk size settings, and it only
has half the expected disk size.
I then create another ploop CT and it contains the expected amount of
disk space.
If the 2nd CT which I created failed to get the requested disk space
due to shortage on the system, then it's difficult to see how the 3rd
CT could then get the full disk space requested. So there seems to be
something funny going on with the disk size calculation of simfs CTs
in stab54.2.
Ploop images grow on demand, similar to sparse files. You can create a
ploop device of 100 GB even when you have only 50 GB free disk space.
Can you please post the output of "df" and "df -i" on the host and from
inside the guest with simfs?
Corin
_______________________________________________
Users mailing list
[email protected]
https://openvz.org/mailman/listinfo/users
