<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 07/22/2014 02:44 PM, Kevin Holly wrote:<br>
<blockquote type="cite">Hi again,<br>
<br>
I just tried to reinstall this container...<br>
The log of that can be found here:<br>
<a class="moz-txt-link-freetext" href="https://ezcrypt.it/Hd9n#SiP14ajsc8sV0SLiGm1diEc1">https://ezcrypt.it/Hd9n#SiP14ajsc8sV0SLiGm1diEc1</a><br>
</blockquote>
<br>
The only strange thing I see is "Killing container", perhaps you use
an incorrect<br>
sequence for vzctl set --userpasswd. Note you do not need to start a
container<br>
to use it. But this is not related, and I guess SolusVM guys are to
blame.<br>
<br>
I failed to reproduce your problem locally:<br>
<br>
# vzctl create 345 --ostemplate ubuntu-12.04-x86_64-minimal --layout
ploop --diskspace 2T<br>
...<br>
vzctl start 345<br>
...<br>
# vzctl exec 345 df -h <br>
Executing command: df -h <br>
Filesystem Size Used Avail Use% Mounted on<br>
/dev/ploop11994p1 2.0T 370M 1.9T 1% /<br>
...<br>
# ploop info /vz/private/345/root.hdd/DiskDescriptor.xml<br>
resource Size Used<br>
1k-blocks 2113785776 378220<br>
inodes 134217728 12599<br>
<br>
<br>
Having said that, I know a way to get to the result you are seeing.
If we run<br>
<br>
vzctl set 345 --diskspace 256G --save<br>
(or perhaps vzctl set --applyconfig with config containing
DISKSPACE parameter)<br>
<br>
it will result in something that you see -- a partition of 2G with a
filesystem of about 256G.<br>
The reason is when shrinking FS ploop uses a hidden balloon rather
than a real resize --<br>
it is much more efficient this way.<br>
<br>
So, can you please provide a sequence of commands to lead<br>
to the problem (starting from vzctl create or earlier)? I understand
you<br>
are using SolusVM, but in order to demonstrate that there is a issue
in OpenVZ<br>
we should try to eliminate extra variables.<br>
<br>
Final question, just curious -- are you paying to SolusVM? If yes,
why don't you use their support<br>
to help with your issues, relying on a free help from OpenVZ
community and deveopers<br>
instead?<br>
<br>
Regards,<br>
Kir.<br>
<br>
<blockquote type="cite"><br>
There is not much difference with the ploop filesystem now. Same
size<br>
(2TB but only 219GiB/235GB available) and "ploop info" on the<br>
DiskDescriptor.xml also reports "1k-blocks 229233640" (wrong
size).<br>
<br>
On 22/07/14 21:27, Kevin Holly wrote:<br>
> Hi,<br>
<br>
> I have a customer complaining about his filesystem being too
small<br>
> (product FS size: 250GB, his FS size: 219GiB / 235GB).<br>
<br>
> After further debugging this issue I am now here:<br>
<br>
<br>
> Creation of the containers filesystem (I can provide more
logs, by<br>
> default I have LOG_LEVEL=7 and VERBOSE=1<br>
<br>
> 2014-06-16T19:20:02+0200 vzctl : CT 2671 : Creating image:<br>
> /vz/private/2671.tmp/root.hdd/root.hdd size=262144000K<br>
> 2014-06-16T19:20:02+0200 : Creating delta<br>
> /vz/private/2671.tmp/root.hdd/root.hdd bs=2048 size=524288000
sectors v2<br>
> 2014-06-16T19:20:02+0200 : Adding snapshot<br>
> {5fbaabe3-6958-40ff-92a7-860e329aab41}<br>
> 2014-06-16T19:20:02+0200 : Storing<br>
> /vz/private/2671.tmp/root.hdd/DiskDescriptor.xml<br>
> 2014-06-16T19:20:02+0200 : Opening delta<br>
> /vz/private/2671.tmp/root.hdd/root.hdd<br>
> 2014-06-16T19:20:02+0200 : Adding delta dev=/dev/ploop16059<br>
> img=/vz/private/2671.tmp/root.hdd/root.hdd (rw)<br>
> 2014-06-16T19:20:02+0200 : Running: parted -s /dev/ploop16059
mklabel<br>
> gpt mkpart primary 1048576b 268434407423b<br>
> 2014-06-16T19:20:02+0200 : Running: mkfs -t ext4 -j -b4096<br>
> -Elazy_itable_init,resize=4294967295 -Jsize=128 -i16384
/dev/ploop16059p1<br>
> 2014-06-16T19:20:03+0200 : Running: /sbin/tune2fs
-ouser_xattr,acl -c0<br>
> -i0 /dev/ploop16059p1<br>
> 2014-06-16T19:20:03+0200 : Creating balloon file<br>
> .balloon-c3a5ae3d-ce7f-43c4-a1ea-c61e2b4504e8<br>
> 2014-06-16T19:20:03+0200 : Mounting /dev/ploop16059p1 at<br>
> /vz/private/2671.tmp/root.hdd/root.hdd.mnt fstype=ext4
data=''<br>
> 2014-06-16T19:20:03+0200 : Unmounting device /dev/ploop16059<br>
> 2014-06-16T19:20:03+0200 : Opening delta<br>
> /vz/private/2671.tmp/root.hdd/root.hdd<br>
> 2014-06-16T19:20:03+0200 : Adding delta dev=/dev/ploop16059<br>
> img=/vz/private/2671.tmp/root.hdd/root.hdd (rw)<br>
> 2014-06-16T19:20:03+0200 : Mounting /dev/ploop16059p1 at
/vz/root/2671<br>
> fstype=ext4 data='balloon_ino=12,'<br>
<br>
<br>
> solus-ed-ch01:~# vzctl exec 2671 df -B1 /<br>
> Executing command: df -B1 /<br>
> Filesystem 1B-blocks Used Available Use%
Mounted on<br>
> /dev/ploop16059p1 234735247360 86872219648 134441467904 40%
/<br>
> solus-ed-ch01:~# vzctl exec 2671 df -h /<br>
> Executing command: df -h /<br>
> Filesystem Size Used Avail Use% Mounted on<br>
> /dev/ploop16059p1 219G 81G 126G 40% /<br>
<br>
<br>
> solus-ed-ch01:~# gdisk -l /dev/ploop16059<br>
> GPT fdisk (gdisk) version 0.8.10<br>
<br>
> Partition table scan:<br>
> MBR: protective<br>
> BSD: not present<br>
> APM: not present<br>
> GPT: present<br>
<br>
> Found valid GPT with protective MBR; using GPT.<br>
> Disk /dev/ploop16059: 4194304000 sectors, 2.0 TiB<br>
> Logical sector size: 512 bytes<br>
> Disk identifier (GUID): FA4B229E-10F7-4583-8A4F-C7B99A34945D<br>
> Partition table holds up to 128 entries<br>
> First usable sector is 34, last usable sector is 4194303966<br>
> Partitions will be aligned on 2048-sector boundaries<br>
> Total free space is 4029 sectors (2.0 MiB)<br>
<br>
> Number Start (sector) End (sector) Size Code Name<br>
> 1 2048 4194301951 2.0 TiB 0700
primary<br>
<br>
<br>
<br>
> So here you can see that the ploop device got provisioned
with 2TB<br>
> ploop filesystem size and the container only sees
234735247360 Byte<br>
> (235 GB / 219 GiB).<br>
<br>
<br>
> Can someone help me debugging this issue further?<br>
<br>
> This host node had no crashes yet, all other containers are
working<br>
> completely fine. It's running the following (patched) kernel
version:<br>
<br>
> solus-ed-ch01:~# uname -a<br>
> Linux solus-ed-ch01 2.6.32-042stab090.2 #1 SMP Wed May 21
19:25:03 MSK<br>
> 2014 x86_64 x86_64 x86_64 GNU/Linux<br>
> solus-ed-ch01:~# kcare-uname -a<br>
> Linux solus-ed-ch01 2.6.32-042stab092.2 #1 SMP Wed May 21
19:25:03 MSK<br>
> 2014 x86_64 x86_64 x86_64 GNU/Linux<br>
<br>
<br>
> Thanks in advance for anyone trying to help!<br>
<br>
<br>
> Best regards<br>
<br>
> Kevin Holly - <a class="moz-txt-link-abbreviated" href="mailto:root@hallowe.lt">root@hallowe.lt</a> - <a class="moz-txt-link-freetext" href="http://hallowe.lt/">http://hallowe.lt/</a><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:Users@openvz.org">Users@openvz.org</a><br>
> <a class="moz-txt-link-freetext" href="https://lists.openvz.org/mailman/listinfo/users">https://lists.openvz.org/mailman/listinfo/users</a><br>
<br>
<br>
</blockquote>
<span style="white-space: pre;">>
_______________________________________________<br>
> Users mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:Users@openvz.org">Users@openvz.org</a><br>
> <a class="moz-txt-link-freetext" href="https://lists.openvz.org/mailman/listinfo/users">https://lists.openvz.org/mailman/listinfo/users</a></span><br>
<br>
<br>
</body>
</html>