<div dir="ltr">Any news on this?<div><span style="font-size:12.8000001907349px">> We know this problem and going to fix it in a near future.</span><br style="font-size:12.8000001907349px"></div><div><br></div><div>I'm just going through our servers and are quite surprised how much diskspace seems to be wasted.</div><div><br></div><div>Take for example this VE with a disk of nominally 292G, 235G used</div><div><br></div><div><div><font face="monospace, monospace"># df -h</font></div><div><font face="monospace, monospace">Filesystem Size Used Avail Use% Mounted on</font></div><div><font face="monospace, monospace">/dev/ploop50951p1 292G 235G 42G 85% /</font></div><div><br></div></div><div>but if I go to /vz/private/2202/root.hdd I find</div><div><br></div><div><div><font face="monospace, monospace">4.0K DiskDescriptor.xml</font></div><div><font face="monospace, monospace">0 DiskDescriptor.xml.lck</font></div><div><font face="monospace, monospace">300G root.hdd</font></div><div><font face="monospace, monospace">161G root.hdd.{8c40287b-2e17-45d1-b58f-1119b3b58b53}</font></div><div><font face="monospace, monospace">138G root.hdd.{fb7ba001-cb78-4dd3-9ac8-cb0c8cbab4f6}</font></div></div><div><br></div><div><div>It doesn't seem that there are any snapshots though, so I guess somehow some of these files are orphans? </div><div><br></div><div><font face="monospace, monospace"># vzctl snapshot-list 2202</font></div><div><font face="monospace, monospace">PARENT_UUID C UUID DATE NAME</font></div><div><font face="monospace, monospace"> * {a684e175-e9a0-4e22-aece-98a11081e2f0} 2014-08-10 18:00:01</font></div></div><div><br></div><div>Any way I can check what is safe to delete?<br></div><div><br></div><div>I already rand a vzctl compact on the VE but it didn't release any more diskspace.</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 23, 2013 at 12:22 PM, Rene C. <span dir="ltr"><<a href="mailto:openvz@dokbua.com" target="_blank">openvz@dokbua.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Good answer, thanks much!!<br>
<br>
<br>
On Mon, Dec 23, 2013 at 4:47 PM, Andrew Vagin <<a href="mailto:avagin@parallels.com">avagin@parallels.com</a>> wrote:<br>
> On Mon, Dec 23, 2013 at 04:28:14PM +0700, Rene C. wrote:<br>
>> Indeed, that seems to have been at least part of the problem, thanks much.<br>
>><br>
>> Still, after having removed all snapshots and rerun vzctl compress, I<br>
>> still ended up with a pigz compressed backup of 40G for a container<br>
>> with 2G used disk space (shown by df -h within the container). Any<br>
>> idea how that can happen?<br>
><br>
> Yes, I have. The size of ploop clusters is 1MB. It's much bigger than<br>
> a file system block size (4KB). The file system can allocate 1 block<br>
> (4K), but one cluster (1Mb) on ploop will be allocated.<br>
><br>
> If a file system spreads blocks far from each other, it can freeze much<br>
> more space in ploop image.<br>
><br>
> We know this problem and going to fix it in a near future.<br>
><br>
>><br>
>> On Sat, Dec 21, 2013 at 11:13 PM, Andrew Vagin <<a href="mailto:avagin@parallels.com">avagin@parallels.com</a>> wrote:<br>
>> > On Sat, Dec 21, 2013 at 09:08:43PM +0700, Rene C. wrote:<br>
>> >> We have a container that needs moving to another hardware node, but a<br>
>> >> vzpbackup of it is 250G.<br>
>> >><br>
>> >> Within the container only 1.9G is used:<br>
>> >><br>
>> >> /dev/ploop33244p1 393G 1.9G 371G 1% /<br>
>> >><br>
>> >> Tried running a vzctl compact but it just shows a few lines and stops<br>
>> >> without having done anything:<br>
>> >><br>
>> >> # vzctl compact 1709<br>
>> >> Trying to find free extents bigger than 0 bytes<br>
>> >> Waiting<br>
>> >> Call FITRIM, for minlen=33554432<br>
>> >> Call FITRIM, for minlen=16777216<br>
>> >> Call FITRIM, for minlen=8388608<br>
>> >> Call FITRIM, for minlen=4194304<br>
>> >> Call FITRIM, for minlen=2097152<br>
>> >> Call FITRIM, for minlen=1048576<br>
>> >> 0 clusters have been relocated<br>
>> >><br>
>> >> /vza1/private/1709/root.hdd has following files:<br>
>> >><br>
>> >> -rw-r--r-- 1 root root 1478 Dec 21 20:35 DiskDescriptor.xml<br>
>> >> -rw------- 1 root root 0 Nov 27 12:33 DiskDescriptor.xml.lck<br>
>> >> -rw------- 1 root root 257 447 428 096 Dec 20 07:42 root.hdd<br>
>> >> -rw------- 1 root root 376 438 784 Dec 20 09:27 root.hdd.{e66fccca-85cf-4bf2-888d-6669988f1da6}<br>
>> >> -rw------- 1 root root 517 996 544 Dec 21 17:49 root.hdd.{f881c603-48cd-4e21-af63-45e49ce715ba}<br>
>> >> drwx------ 2 root root 4096 Nov 27 12:34 root.hdd.mnt<br>
>> >><br>
>> >> What can we do to compress this down to the actual 2G used?<br>
>> ><br>
>> > Looks like you did a snapshot, didn't you? In this case only the last<br>
>> > delta is compacted.<br>
>> ><br>
>> > You can try to delete snapshots and compress the disk again.<br>
>> ><br>
>> >><br>
>> >> 2.6.32-042stab081.5<br>
>> >> e2fsprogs-resize2fs-static-1.42.3-3.el6.1.ovz.x86_64<br>
>> >> vzctl-4.5.1-1.x86_64<br>
>> >> vzkernel-2.6.32-042stab081.5.x86_64<br>
>> >> vzctl-core-4.5.1-1.x86_64<br>
>> >> vzquota-3.1-1.x86_64<br>
>> >> vzstats-0.5.2-1.noarch<br>
>> >> ploop-lib-1.9-1.x86_64<br>
>> >> ploop-1.9-1.x86_64<br>
>> >> _______________________________________________<br>
>> >> Users mailing list<br>
>> >> <a href="mailto:Users@openvz.org">Users@openvz.org</a><br>
>> >> <a href="https://lists.openvz.org/mailman/listinfo/users" target="_blank">https://lists.openvz.org/mailman/listinfo/users</a><br>
</blockquote></div><br></div>