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

[GH-ISSUE #2943] Deprecate the Usage of the : separator in favor of - regardless of OS for maximum compatibility #63844

New Issue
Closed
opened 2026-05-03 15:10:31 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-03 15:10:31 -05:00
Owner
Copy Link

Originally created by @LumiWasTaken on GitHub (Mar 6, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/2943

Heyo!

Here the short summary:
We have a system which uses a file system that runs on both windows and linux for and basically both Run Ollama but access the same model storage to save storage.

Or so we planned.

On Linux Ollama expects the sha256 blob filenames to be separated with a colon sha256:abcdefg... while on Windows it expects a dash sha256-abcdefg... while this makes sense as colons are an illegal character in filenames on NTFS drives. It causes quite a spark when it comes to compatibility.

So I'd ask for the following proposal:
Add a Fallback compatibility, existing files using the colon will still be supported.
Future blobs will use the dash.
Extra: At some point add a renaming where it renames : to -.

This would ensure future compatibility if Ollama Windows turns out to be more mainstream or if the storage of Models would be on a external storage (NTFS formatted USB sticks, SMB Shares on Windows Servers etc.)

Originally created by @LumiWasTaken on GitHub (Mar 6, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/2943 Heyo! Here the short summary: We have a system which uses a file system that runs on both windows and linux for and basically both Run Ollama but access the same model storage to save storage. Or so we planned. On Linux Ollama expects the sha256 blob filenames to be separated with a colon `sha256:abcdefg...` while on Windows it expects a dash `sha256-abcdefg...` while this makes sense as colons are an illegal character in filenames on NTFS drives. It causes quite a spark when it comes to compatibility. So I'd ask for the following proposal: Add a Fallback compatibility, existing files using the colon will still be supported. Future blobs will use the dash. Extra: At some point add a renaming where it renames `:` to `-`. This would ensure future compatibility if Ollama Windows turns out to be more mainstream or if the storage of Models would be on a external storage (NTFS formatted USB sticks, SMB Shares on Windows Servers etc.)
GiteaMirror added the feature request label 2026-05-03 15:10:31 -05:00
GiteaMirror commented 2026-05-03 15:11:16 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (Mar 13, 2024):

Let's track this separator cleanup via #2032

<!-- gh-comment-id:1994893530 --> @dhiltgen commented on GitHub (Mar 13, 2024): Let's track this separator cleanup via #2032
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 feature 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#63844
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?