github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-07 08:30:05 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[PR #9489] [MERGED] server/internal/registry: reintroduce pruning on model deletion #59684

New Issue
Closed
opened 2026-04-29 14:37:17 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-29 14:37:17 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/9489
Author: @bmizerany
Created: 3/4/2025
Status: ✅ Merged
Merged: 3/4/2025
Merged by: @bmizerany

Base: main ← Head: bmizerany/pruneonrmagain

📝 Commits (1)

  • f1dc37a server/internal/registry: reintroduce pruning on model deletion

📊 Changes

2 files changed (+10 additions, -1 deletions)

View changed files

📝 server/internal/registry/server.go (+8 -1)
📝 server/routes.go (+2 -0)

📄 Description

This reintroduces aggressive pruning on model deletion as a temporary
measure until a more controlled garbage collection (GC) mechanism is
implemented.

Issues with the current approach:

  1. Users may accidentally delete a model (ollama rm llama3.3 instead
    of ollama rm llama3.2), requiring a full re-download unless another
    model references the same blobs.

  2. Users may assume a deleted model is still referenced elsewhere, but
    due to prior updates or deletions, the references no longer exist,
    leading to unnecessary re-downloads.

Soon, we should implement a structured GC mechanism to retain
unreferenced blobs for a configurable period before removal, which will
run on "ollama rm" and other commands we deem appropriate.

Users that want to immediately remove unreferenced blobs can use a new
prune command that will allow them to specify the age and class of blobs
to remove.

Example usage:

# Run basic blob GC
$ ollama prune

# Remove unreferenced blobs older than 7 days
$ ollama prune --age 7d

# Remove all blobs, referenced or not, older than 7 days (and their manifests?)
$ ollama prune --age 7d --all

# Remove all unreferenced blobs immediately
$ ollama prune --age 0 --all

# Remove all blobs
$ ollama prune --age 0 --all

This should provide a safer and more predictable cleanup process.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/ollama/ollama/pull/9489 **Author:** [@bmizerany](https://github.com/bmizerany) **Created:** 3/4/2025 **Status:** ✅ Merged **Merged:** 3/4/2025 **Merged by:** [@bmizerany](https://github.com/bmizerany) **Base:** `main` ← **Head:** `bmizerany/pruneonrmagain` --- ### 📝 Commits (1) - [`f1dc37a`](https://github.com/ollama/ollama/commit/f1dc37a015e60a40705aafca845193fb50b75593) server/internal/registry: reintroduce pruning on model deletion ### 📊 Changes **2 files changed** (+10 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `server/internal/registry/server.go` (+8 -1) 📝 `server/routes.go` (+2 -0) </details> ### 📄 Description This reintroduces aggressive pruning on model deletion as a temporary measure until a more controlled garbage collection (GC) mechanism is implemented. Issues with the current approach: 1. Users may accidentally delete a model (`ollama rm llama3.3` instead of `ollama rm llama3.2`), requiring a full re-download unless another model references the same blobs. 2. Users may assume a deleted model is still referenced elsewhere, but due to prior updates or deletions, the references no longer exist, leading to unnecessary re-downloads. Soon, we should implement a structured GC mechanism to retain unreferenced blobs for a configurable period before removal, which will run on "ollama rm" and other commands we deem appropriate. Users that want to immediately remove unreferenced blobs can use a new prune command that will allow them to specify the age and class of blobs to remove. Example usage: # Run basic blob GC $ ollama prune # Remove unreferenced blobs older than 7 days $ ollama prune --age 7d # Remove all blobs, referenced or not, older than 7 days (and their manifests?) $ ollama prune --age 7d --all # Remove all unreferenced blobs immediately $ ollama prune --age 0 --all # Remove all blobs $ ollama prune --age 0 --all This should provide a safer and more predictable cleanup process. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-29 14:37:17 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#59684
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?