Originally created by @kha84 on GitHub (Feb 27, 2024).
Is your feature request related to a problem? Please describe.
If you run ollama run/pull <some_new_model_you_didnt_have> and then for whatever reason the downloading stops in-between, the unfinished files are left (supposedly) in ~/.ollama/models/blobs/sha256:-partial occupying quite a lot of space (depending on when the stop happened). Running ollama list doesn't show those unfinished downloads - so you don't see them, can't remove them. This leads to the hdd space wastage without user knowing
Describe the solution you'd like
There should be a way for ollama to trigger (automatically, every once in a while) a reconcile procedure, to identify and remove whatever files are related to unfinished downloads.
Describe alternatives you've considered
Manually deleting files related to unfinished downloads (might be tricky for users, because the info about where ollama holds all it's internals and how it's organized isn't part of official documentation - it's kinda hidden under the hood)
ollama list to show unfinished downloads so they could be deleted with ollama rm
Originally created by @kha84 on GitHub (Feb 27, 2024).
**Is your feature request related to a problem? Please describe.**
If you run `ollama run/pull <some_new_model_you_didnt_have>` and then for whatever reason the downloading stops in-between, the unfinished files are left (supposedly) in ~/.ollama/models/blobs/sha256:*-partial* occupying quite a lot of space (depending on when the stop happened). Running `ollama list` doesn't show those unfinished downloads - so you don't see them, can't remove them. This leads to the hdd space wastage without user knowing
**Describe the solution you'd like**
There should be a way for ollama to trigger (automatically, every once in a while) a **reconcile** procedure, to identify and remove whatever files are related to unfinished downloads.
**Describe alternatives you've considered**
1) Manually deleting files related to unfinished downloads (might be tricky for users, because the info about where ollama holds all it's internals and how it's organized isn't part of official documentation - it's kinda hidden under the hood)
2) `ollama list` to show unfinished downloads so they could be deleted with `ollama rm`
Please close this issue, this is not the Ollama project GitHub, and Open WebUI is not affiliated with them.
@justinh-rahb commented on GitHub (Feb 27, 2024):
Please close this issue, this is not the Ollama project GitHub, and Open WebUI is not affiliated with them.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @kha84 on GitHub (Feb 27, 2024).
Is your feature request related to a problem? Please describe.
If you run
ollama run/pull <some_new_model_you_didnt_have>and then for whatever reason the downloading stops in-between, the unfinished files are left (supposedly) in ~/.ollama/models/blobs/sha256:-partial occupying quite a lot of space (depending on when the stop happened). Runningollama listdoesn't show those unfinished downloads - so you don't see them, can't remove them. This leads to the hdd space wastage without user knowingDescribe the solution you'd like
There should be a way for ollama to trigger (automatically, every once in a while) a reconcile procedure, to identify and remove whatever files are related to unfinished downloads.
Describe alternatives you've considered
ollama listto show unfinished downloads so they could be deleted withollama rm@justinh-rahb commented on GitHub (Feb 27, 2024):
Please close this issue, this is not the Ollama project GitHub, and Open WebUI is not affiliated with them.
@kha84 commented on GitHub (Mar 3, 2024):
Ah sorry mates, I'm blind and posted the issue in the wrong repo :(