[GH-ISSUE #12221] [bug] Older Blobs are not deleted when updating a model #70191

Closed
opened 2026-05-04 20:37:38 -05:00 by GiteaMirror · 6 comments
Owner

Originally created by @fbestenli on GitHub (Sep 8, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/12221

Hi, I had an older release for gemma3:27b 30ddded7fba6, I updated to the latest release version a418f5838eaf. I checked the disk space before and after and I found that the older blobs were not replaced by the new ones. I have a lot of model installed so it's not possible to me to manually know and delete the sha256- files that are related to the older version. I'm running Windows 11 with latest version of Ollama 0.11.10. Is this a known issue?

Originally created by @fbestenli on GitHub (Sep 8, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/12221 Hi, I had an older release for gemma3:27b `30ddded7fba6`, I updated to the latest release version `a418f5838eaf`. I checked the disk space before and after and I found that the older blobs were not replaced by the new ones. I have a lot of model installed so it's not possible to me to manually know and delete the `sha256-` files that are related to the older version. I'm running Windows 11 with latest version of Ollama `0.11.10`. Is this a known issue?
Author
Owner

@rick-github commented on GitHub (Sep 8, 2025):

You likely have an alias that refers to the previous model. ollama list will show all models, locate the ones with id of 30ddded7fba6 and delete them.

<!-- gh-comment-id:3268362982 --> @rick-github commented on GitHub (Sep 8, 2025): You likely have an alias that refers to the previous model. `ollama list` will show all models, locate the ones with id of 30ddded7fba6 and delete them.
Author
Owner

@fbestenli commented on GitHub (Sep 8, 2025):

No I already checked that of course!
ollama list will show only the new model (which replaced the old one).
There is no any model having the previous ID I saved from ollama list before updating in the new list.

<!-- gh-comment-id:3268382887 --> @fbestenli commented on GitHub (Sep 8, 2025): No I already checked that of course! `ollama list` will show only the new model (which replaced the old one). There is no any model having the previous ID I saved from `ollama list` before updating in the new list.
Author
Owner

@rick-github commented on GitHub (Sep 8, 2025):

Restarting the ollama server will delete blobs that are no longer associated with a model.

<!-- gh-comment-id:3268389619 --> @rick-github commented on GitHub (Sep 8, 2025): Restarting the ollama server will delete blobs that are no longer associated with a model.
Author
Owner

@fbestenli commented on GitHub (Sep 9, 2025):

I tried that as well, it doesn't. Please don't suggest something you haven't tried!

<!-- gh-comment-id:3268474819 --> @fbestenli commented on GitHub (Sep 9, 2025): I tried that as well, it doesn't. Please don't suggest something you haven't tried!
Author
Owner

@rick-github commented on GitHub (Sep 9, 2025):

I have tried it. Do you have OLLAMA_NOPRUNE set?

<!-- gh-comment-id:3268477112 --> @rick-github commented on GitHub (Sep 9, 2025): I have tried it. Do you have `OLLAMA_NOPRUNE` set?
Author
Owner

@fbestenli commented on GitHub (Sep 9, 2025):

hmm, I totally forgot that I have put it since long time. I set it to false now and restarting seems to delete blobs now.
Sorry that was my mistake then! Thanks a lot!

<!-- gh-comment-id:3268489368 --> @fbestenli commented on GitHub (Sep 9, 2025): hmm, I totally forgot that I have put it since long time. I set it to `false` now and restarting seems to delete blobs now. Sorry that was my mistake then! Thanks a lot!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#70191