-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LFS exists on the server, but it doesn't work properly (missing in database) #32929
Comments
It means that it doesn't exit in database. You could try to |
那我几十个代码仓库都需要做这个事情,而且,还有很多仓库是并没有克隆到本地的,无法执行git lfs push --all Then I need dozens of code repositories to do this, and there are many repositories that are not cloned locally and cannot execute git lfs push --all |
Then maybe need to figure out how to recover the database records |
Yes, do you know how you can help me? |
Description
I've encountered a problem. I've searched all over the Internet but haven't found a solution. The LFS files do exist on the server. When I clone them down and check the sha256, I can find the LFS files on the server. However, Gitea prompts that the LFS files are missing. If I clone them again, it will also prompt that the LFS files don't exist. Just because I manually renamed the git/lfs folder and then changed it back, what should I do? Now the LFS of all repositories doesn't work. Is there anyone who can help me solve this problem? The LFS files are all on the server, but Gitea insists that they don't exist. What should I do? I'm really worried.
Gitea Version
22.6.0 built with GNU Make 4.4.1, go1.22.10 : bindata, sqlite, sqlite_unlock_notify
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
Git Version
git version 2.45.2
Operating System
Host Debian
How are you running Gitea?
Docker official image
Database
MySQL/MariaDB
The text was updated successfully, but these errors were encountered: