Good catch. The bug was inside the implementation of `-availableSpace`, and that was the essential fix. IIRC, these were call sites that *should* have been using that shared method, but repeated the incorrect calculation. Looks like I messed up these two call sites and should have completely replace the right hand side with `[self availableSpace]`.