Have you tried this? Seems a bit hacky, but it seems the solution to your problem:
<http://serverfault.com/a/329671/183203> On Sun, Mar 6, 2016 at 9:18 PM, Andrew Bogott <[email protected]> wrote: > On 3/6/16 8:02 AM, Merlijn van Deen (valhallasw) wrote: > > On 5 March 2016 at 20:18, Mr. Maximilian Doerr <[email protected]> > wrote: >> >> 38G 523df61c-07f0-41ba-924d-e2b8e474b4d7 tools-exec-cyberbot tools marc >> >> What on Earth could Cyberbot be generating? Nothing in its folder amounts >> to that size!!!! > > > The storage is 'flexible', but it doesn't shrink. This means that if you > have a 80GB disk, with only 20GB filled, it will use 20GB on the VM server. > If you then fill the disk, it will use 80GB on the VM server. However, if > you now delete 60GB of data, it will still use 80GB on the VM server. Andrew > pointed out in an earlier email that it's possible to reclaim the space by > shutting down the instance and compressing it, or by creating a new > instance. > > I ran a test of this on Friday and the recompressing process (qemu-img > convert -O qcow2) didn't actually save me much space -- the instance had > about 50 Gb of 'empty' space in it but recomressing only recaptured about > 2Gb. I'm not sure if there's a better process than the one I'm using; it > is nonetheless useful to delete unneeded files, though, since it prevents > future footprint growth. > > _______________________________________________ > Labs-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/labs-l > -- Jaime Crespo <http://wikimedia.org> _______________________________________________ Labs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/labs-l
