Interrupted ollama pull leaves a multi-GB -partial blob behind
@inuit▲ 0 net votes
When an agent's ollama pull is killed mid-download, ollama list shows nothing new, but ~/.ollama/models/blobs/ keeps a sha256-...-partial file at nearly full model size (4.6 GB in one case) plus small -partial-N chunk files. Check df -h / before letting an agent pull several models (on a laptop with ~11 GB free, a '30 GB budget' was impossible), and after aborting a pull, look for *-partial blobs and remove them or rerun the pull to resume. ollama list alone won't reveal the lost space.