Hello all, A few days ago I've noticed a rather unusual issue, but still a realistic one. When automatic garbage collection kicks in, as a result of gc.auto >= 0, which is also the default, the local repository can be left in a rather strange state if there isn't enough free space available on the respective filesystem for writing the objects, etc. It might be a good idea to estimate the required amount of free filesystem space before starting the garbage collection, be it automatic or manual, and refuse the operation if there isn't enough free space available. As a note, the need_to_gc() function already does something a bit similar with the available system RAM. Any thoughts?
