github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

gitea lfs Storage error #13146

New Issue
Closed
opened 2025-11-02 10:32:40 -06:00 by GiteaMirror · 15 comments
GiteaMirror commented 2025-11-02 10:32:40 -06:00
Owner
Copy Link

Originally created by @WangZhongDian on GitHub (Jun 13, 2024).

Description

question

I created a test repository to describe my problem. After completing the initialization work of LFS, there was a ttf file and a pth file inside, both of which were tracked by LFS. When uploaded to Gitea, the ttf file was normal, while the pth error was 500. However, there was a pointer to the pth file in the backend/data/git/lfs. I compared this on Github, which is completely normal
图片
图片
图片

github

图片
图片

Gitea Version

1.22

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

2.43.0

Operating System

ubuntu24.04

How are you running Gitea?

docker

Database

SQLite

Originally created by @WangZhongDian on GitHub (Jun 13, 2024). ### Description # question I created a test repository to describe my problem. After completing the initialization work of LFS, there was a ttf file and a pth file inside, both of which were tracked by LFS. When uploaded to Gitea, the ttf file was normal, while the pth error was `500`. However, there was a pointer to the pth file in the backend`/data/git/lfs`. I compared this on Github, which is completely normal ![图片](https://github.com/go-gitea/gitea/assets/103353084/7cf0fe0e-f252-4fe7-a3df-6d1b29a30219) ![图片](https://github.com/go-gitea/gitea/assets/103353084/829b99e6-12ee-4714-90a4-2bdfa4956e96) ![图片](https://github.com/go-gitea/gitea/assets/103353084/2cba6bb7-f0b1-4a88-862d-c74313cf1e3c) ## github ![图片](https://github.com/go-gitea/gitea/assets/103353084/91d9eacd-81af-41e4-ab39-fff3c23257c1) ![图片](https://github.com/go-gitea/gitea/assets/103353084/c4892e03-2600-434e-aa7b-02198019fc9e) ### Gitea Version 1.22 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version 2.43.0 ### Operating System ubuntu24.04 ### How are you running Gitea? docker ### Database SQLite
GiteaMirror added the topic/lfsissue/needs-feedback labels 2025-11-02 10:32:40 -06:00
GiteaMirror commented 2025-11-02 10:32:42 -06:00
Author
Owner
Copy Link

@MaxWaldorf commented on GitHub (Jun 15, 2024):

I confirm same behavior here... pushing lfs is impossible...

@MaxWaldorf commented on GitHub (Jun 15, 2024): I confirm same behavior here... pushing lfs is impossible...
GiteaMirror commented 2025-11-02 10:32:42 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jun 16, 2024):

I am also using Gitea LFS in my team, and haven't encounter any problem.

Could you provide a reproducible setup (a docker-compose) with detailed steps (step by step and the files)? If I could reproduce it on my machine, then I could try to debug it.

@wxiaoguang commented on GitHub (Jun 16, 2024): I am also using Gitea LFS in my team, and haven't encounter any problem. Could you provide a reproducible setup (a docker-compose) with detailed steps (step by step and the files)? If I could reproduce it on my machine, then I could try to debug it.
GiteaMirror commented 2025-11-02 10:32:42 -06:00
Author
Owner
Copy Link

@WangZhongDian commented on GitHub (Jun 16, 2024):

@wxiaoguang
I feel that there is only a problem with the. pth file. Have you tried uploading the. pth file in pytorch format

@WangZhongDian commented on GitHub (Jun 16, 2024): @wxiaoguang I feel that there is only a problem with the. pth file. Have you tried uploading the. pth file in pytorch format
GiteaMirror commented 2025-11-02 10:32:42 -06:00
Author
Owner
Copy Link

@WangZhongDian commented on GitHub (Jun 16, 2024):

It seems that this issue only occurs when tracking *. pth files

@WangZhongDian commented on GitHub (Jun 16, 2024): It seems that this issue only occurs when tracking` *. pth` files
GiteaMirror commented 2025-11-02 10:32:43 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jun 16, 2024):

@wxiaoguang I feel that there is only a problem with the. pth file. Have you tried uploading the. pth file in pytorch format

I do not think it is a general problem, because Gitea itself have no special code for "file extension" or "file content".

So the question is: how to reproduce? Is it related to the file size? File content (deleted by antivirus software)? Or something else (firewall)?

Does every pth file get lost in your environment, or some special ones get lost?

@wxiaoguang commented on GitHub (Jun 16, 2024): > @wxiaoguang I feel that there is only a problem with the. pth file. Have you tried uploading the. pth file in pytorch format I do not think it is a general problem, because Gitea itself have no special code for "file extension" or "file content". So the question is: how to reproduce? Is it related to the file size? File content (deleted by antivirus software)? Or something else (firewall)? Does every pth file get lost in your environment, or some special ones get lost?
GiteaMirror commented 2025-11-02 10:32:43 -06:00
Author
Owner
Copy Link

@WangZhongDian commented on GitHub (Jun 16, 2024):

@wxiaoguang
I am currently unable to determine the root cause of the problem. When I click on this file, an error of 500 will appear
图片

@WangZhongDian commented on GitHub (Jun 16, 2024): @wxiaoguang I am currently unable to determine the root cause of the problem. When I click on this file, an error of `500` will appear ![图片](https://github.com/go-gitea/gitea/assets/103353084/d74fd8d5-e2e3-4294-aea4-c760a29ac3a7)
GiteaMirror commented 2025-11-02 10:32:43 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jun 16, 2024):

@wxiaoguang
I am currently unable to determine the root cause of the problem. When I click on this file, an error of 500 will appear

So could you provide a reproducible setup (a docker-compose) with detailed steps (step by step and the files)? If I could reproduce it on my machine, then I could try to debug it.

@wxiaoguang commented on GitHub (Jun 16, 2024): > @wxiaoguang > I am currently unable to determine the root cause of the problem. When I click on this file, an error of `500` will appear So could you provide a reproducible setup (a docker-compose) with detailed steps (step by step and the files)? If I could reproduce it on my machine, then I could try to debug it.
GiteaMirror commented 2025-11-02 10:32:43 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jun 16, 2024):

ps: if you couldn't reproduce on your local setup either, then it should be related to your server environment (eg: antivirus software, firewall, etc)

@wxiaoguang commented on GitHub (Jun 16, 2024): ps: if you couldn't reproduce on your local setup either, then it should be related to your server environment (eg: antivirus software, firewall, etc)
GiteaMirror commented 2025-11-02 10:32:43 -06:00
Author
Owner
Copy Link

@WangZhongDian commented on GitHub (Jun 16, 2024):

yolov5_s_v6.1.zip
You can try this file
@wxiaoguang
Docker did not use any special settings, I did not use Docker Compose for orchestration

图片
图片

@WangZhongDian commented on GitHub (Jun 16, 2024): [yolov5_s_v6.1.zip](https://github.com/user-attachments/files/15857311/yolov5_s_v6.1.zip) You can try this file @wxiaoguang Docker did not use any special settings, I did not use `Docker Compose` for orchestration ![图片](https://github.com/go-gitea/gitea/assets/103353084/09bfd483-6351-49de-921e-598f3a967b54) ![图片](https://github.com/go-gitea/gitea/assets/103353084/d4a94f4f-74ff-43a7-ad70-62559d9d302e)
GiteaMirror commented 2025-11-02 10:32:44 -06:00
Author
Owner
Copy Link

@WangZhongDian commented on GitHub (Jun 16, 2024):

My computer is
ubuntu24.04
Kernel: 6.8.0-35 generic
Architecture: x86_64

@WangZhongDian commented on GitHub (Jun 16, 2024): My computer is ubuntu24.04 Kernel: 6.8.0-35 generic Architecture: x86_64
GiteaMirror commented 2025-11-02 10:32:44 -06:00
Author
Owner
Copy Link

@WangZhongDian commented on GitHub (Jun 16, 2024):

If you are unable to reproduce this error, it may be my problem. This Gitea has been upgraded from an old version and I am not sure what internal errors it has experienced

@WangZhongDian commented on GitHub (Jun 16, 2024): If you are unable to reproduce this error, it may be my problem. This Gitea has been upgraded from an old version and I am not sure what internal errors it has experienced
GiteaMirror commented 2025-11-02 10:32:44 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jun 16, 2024):

It works perfectly on my side, and it can be downloaded again by clicking Raw link.

As I suggested above: please check your environment or reproduce it on your side locally.

image

image

image

image

image

image

@wxiaoguang commented on GitHub (Jun 16, 2024): It works perfectly on my side, and it can be downloaded again by clicking Raw link. As I suggested above: please check your environment or reproduce it on your side locally. <details> ![image](https://github.com/go-gitea/gitea/assets/2114189/87c42521-8f5f-4390-812d-603322f22e6f) ![image](https://github.com/go-gitea/gitea/assets/2114189/e4db2c42-59c2-4870-b36e-d333e2e44aac) ![image](https://github.com/go-gitea/gitea/assets/2114189/26938e62-45c1-4c6f-8e96-ee5d3457d482) ![image](https://github.com/go-gitea/gitea/assets/2114189/3dd024de-515c-4a15-af2a-d11973c4ed7a) ![image](https://github.com/go-gitea/gitea/assets/2114189/4af5ded1-0d8a-43dd-8ad0-6e16bd4916f6) ![image](https://github.com/go-gitea/gitea/assets/2114189/43b44b5b-10f1-46f0-8d7a-42e6ef522d26) </details>
GiteaMirror commented 2025-11-02 10:32:44 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jun 16, 2024):

And one more thing, if a file is lost on server, you could try to re-push all LFS contents by git lfs push --all origin main

@wxiaoguang commented on GitHub (Jun 16, 2024): And one more thing, if a file is lost on server, you could try to re-push all LFS contents by `git lfs push --all origin main`
GiteaMirror commented 2025-11-02 10:32:45 -06:00
Author
Owner
Copy Link

@MaxWaldorf commented on GitHub (Jun 16, 2024):

Potentially there is an issue with Wasabi...

@MaxWaldorf commented on GitHub (Jun 16, 2024): Potentially there is an issue with Wasabi...
GiteaMirror commented 2025-11-02 10:32:45 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jun 16, 2024):

I will close this issue since it doesn't seem to be directly related to Gitea. Feel free to reopen if it could be reproduced on a Gitea setup.

@wxiaoguang commented on GitHub (Jun 16, 2024): I will close this issue since it doesn't seem to be directly related to Gitea. Feel free to reopen if it could be reproduced on a Gitea setup.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/needs-feedback topic/lfs
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/gitea#13146
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?