Last modified: 2014-10-27 11:36:48 UTC
Created attachment 16658 [details] Screendump of the error Tried to warp https://commons.wikimedia.org/wiki/File:Patroclus_Hirsch,_Christiania_By_og_dens_Marker,_1794_og_1795,_reproduksjon.tif#.7B.7Bint:filedesc.7D.7D And got an "Out of space". This file is ~200MB
Thanks - there was over 200mb left on the / partition however, it probably needed space in /tmp as well. Will free up some space and move thumbnails (only using 100mb so far) over to shared project directory.
What are steps to reproduce to "warp"? I'm not even sure which server this is about and how to be able to see the same outcome / steps to reproduce.
Okay I have moved the warper uploads, to shared project space, which left around 400mb in the /dev/vda1 partition. When the map is added it goes into /tmp first and I believe that this is being filled up causing the error Smaller sized images won't cause the error, but larger ones will. I think it's possible to change the tmp directory in the warper code. Will investigate. --- Andre - this is on warper.wmflabs.org part of the WikiMaps Commons Project. To reproduce one would need to click a link from the Commons template which had the map template included i.e. https://commons.wikimedia.org/wiki/File:Oslo_byarkiv,_Grosch_1830-%C3%A5rene,_001_001.tif which goes to here: https://warper.wmflabs.org/wikimaps/new?pageid=35599439 which if the map is not in the warper, it would prompt the user to load it in, and it is at this stage that the error is seen. Also the image itself would need to be large i.e. over 200mb which is a small amount of the Commons maps - most are smaller and would work without error Cheers, Tim
This one bombs out https://commons.wikimedia.org/wiki/File:Patroclus_Hirsch,_Christiania_By_og_dens_Marker,_1794_og_1795,_reproduksjon.tif Yes it is large!
So is this something to fix in the warper project itself? Or is this something to fix in the general Labs infrastructure for tools?
Still fails. I think the map warper instance need more disk space.
it's due to the size of the /tmp partition, not the whole instance. The whole instance has enough disk space, it's where /tmp resides which is filling up, but _temporarily_ _temporarily_ /tmp fills up when 1) the system requests a large file from commons and 2) the system converts it into a tif /tmp then will clear out these temporary files, freeing up the space on that partition which is why smaller files run okay. The fix would be to: 1) increase the size of the /tmp partition 2) change the application to use another partition for temporary files. I believe #2 would be possible, but need to investigate properly. Leave the issue open and as new until that has occurred.
