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

[GH-ISSUE #12153] Terrible filenaming (relation between manifest and model files not clear) #8081

New Issue
Closed
opened 2026-04-12 20:22:36 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-12 20:22:36 -05:00
Owner
Copy Link

Originally created by @SkybuckFlying on GitHub (Sep 2, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/12153

What is the issue?

Give files better descriptions.

Not just a bunch of random letters !

(It should be more clear what the relation is between the manifest files and the model files, right now it requires me to search for the sha256 string and manipulate that too because those strings slightly different: sha256: versus sha256-)

Originally created by @SkybuckFlying on GitHub (Sep 2, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/12153 ### What is the issue? Give files better descriptions. Not just a bunch of random letters ! (It should be more clear what the relation is between the manifest files and the model files, right now it requires me to search for the sha256 string and manipulate that too because those strings slightly different: sha256: versus sha256-)
GiteaMirror added the bug label 2026-04-12 20:22:36 -05:00
GiteaMirror commented 2026-04-12 20:22:38 -05:00
Author
Owner
Copy Link

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

The filenames are not random letters, they are the sha256sum of the file contents. Maintaining the model components is normally up to the ollama server and a user is not expected to reference the files directly, hence no sugar coating. What would you like to achieve?

<!-- gh-comment-id:3246082672 --> @rick-github commented on GitHub (Sep 2, 2025): The filenames are not random letters, they are the sha256sum of the file contents. Maintaining the model components is normally up to the ollama server and a user is not expected to reference the files directly, hence no sugar coating. What would you like to achieve?
GiteaMirror commented 2026-04-12 20:22:38 -05:00
Author
Owner
Copy Link

@pdevine commented on GitHub (Sep 2, 2025):

As @rick-github mentioned, you file names are used to maintain the integrity of the file and they're not meant to be used directly by users. You can verify the contents of each of the blobs by typing something like:

% sha2 -256 sha256-1043b744a03d8c3de6f66dbc3ee589c39949268c177969a87c6f413d5af500dc
SHA-256 (sha256-1043b744a03d8c3de6f66dbc3ee589c39949268c177969a87c6f413d5af500dc) = 1043b744a03d8c3de6f66dbc3ee589c39949268c177969a87c6f413d5af500dc

If the sha hash doesn't match the file name, you have a corrupted file.

<!-- gh-comment-id:3246267642 --> @pdevine commented on GitHub (Sep 2, 2025): As @rick-github mentioned, you file names are used to maintain the integrity of the file and they're not meant to be used directly by users. You can verify the contents of each of the blobs by typing something like: ``` % sha2 -256 sha256-1043b744a03d8c3de6f66dbc3ee589c39949268c177969a87c6f413d5af500dc SHA-256 (sha256-1043b744a03d8c3de6f66dbc3ee589c39949268c177969a87c6f413d5af500dc) = 1043b744a03d8c3de6f66dbc3ee589c39949268c177969a87c6f413d5af500dc ``` If the sha hash doesn't match the file name, you have a corrupted file.
GiteaMirror commented 2026-04-12 20:22:39 -05:00
Author
Owner
Copy Link

@SkybuckFlying commented on GitHub (Sep 10, 2025):

It's not just the SHA, it's other files as well and has nothing to do with SHA.

<!-- gh-comment-id:3276274373 --> @SkybuckFlying commented on GitHub (Sep 10, 2025): It's not just the SHA, it's other files as well and has nothing to do with SHA.
GiteaMirror commented 2026-04-12 20:22:40 -05:00
Author
Owner
Copy Link

@pdevine commented on GitHub (Sep 11, 2025):

The files are called sha256- instead of sha256: because some file systems (like for Windows) can't handle files with colons in the file names. Regardless, the files aren't meant to be directly read/used by users.

<!-- gh-comment-id:3281622766 --> @pdevine commented on GitHub (Sep 11, 2025): The files are called `sha256-` instead of `sha256:` because some file systems (like for Windows) can't handle files with colons in the file names. Regardless, the files aren't meant to be directly read/used by users.
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 bug
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#8081
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?