02 May 11, 01:21PM
(This post was last modified: 02 May 11, 01:26PM by GeneralDisarray.)
Thought we fixed that already? I spotted that the code doing the space check was subject to 32-bit truncation if compiled on a 32-bit platform, however since that part is Linux-specific (am on Windows) I couldn't double-check/build the fix so I drew tempest's attention to that... but now I see the fix wasn't commited yet? In any case I can see no reason this won't be fixed for the next release.
EDIT: for now, there's a crude workaround Linux servers owners can use: use up or free up around 100 meg of disk space; the nature of the bug means that for every 4 gig of disk space, there's a 50 meg region that will trigger the error.
EDIT: for now, there's a crude workaround Linux servers owners can use: use up or free up around 100 meg of disk space; the nature of the bug means that for every 4 gig of disk space, there's a 50 meg region that will trigger the error.