Chemical, the change introduced in January simply makes downloads erroneous in the catch block (when I/O errors occur). So much is clear.
What I'd like to find out is why these errors occur in the first place.
Please su to the user running amuled and see how much you can still write to the partition.
Ok, I see. However, as my limit was before on 10MB and is now on 30MB - I would say that the amuled can write at least additional 20MB to the partition. The Erroneous-state continued to exist even after raising the limit by 20MB - this, for my understanding, moves the problem from the hardware/filesystem to the core itself.
The user itself should be able to fill up the disk - I will check this the next time it happens. Additionally to that, I'll raise up to 100MB to be sure it is not the filesystem/IO.