Skip to content
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 upload error:getFileReader, LFS Meta object does not exist #32535

Open
Skodeva opened this issue Nov 16, 2024 · 4 comments
Open

LFS upload error:getFileReader, LFS Meta object does not exist #32535

Skodeva opened this issue Nov 16, 2024 · 4 comments
Labels

Comments

@Skodeva
Copy link

Skodeva commented Nov 16, 2024

Description

Hello, I tested and found that after uploading the AAA.mp3 file in the attached AAA compressed package to Gitea via LFS, the prompt: "getFileReader, LFS Meta object does not exist".

But after re-converting the AAA file through the audio converter, that is, AAAConvert.mp3, Gitea can recognize it normally.

I found similar problems with other files before, but it has been a long time and I don't remember what format the file was.

The steps to reproduce are very simple. Download my attachment and upload it in LFS format to test.

Please check it, thank you!

This is the attachment: AAA.zip

The following is the error interface:
PixPin_2024-11-16_23-15-19

Gitea Version

1.22.3

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

docker

How are you running Gitea?

docker

Database

SQLite

@Skodeva
Copy link
Author

Skodeva commented Nov 16, 2024

After testing, I found that using the code "git lfs push --all origin" can solve this problem.
I don't know why other LFS can be uploaded normally, but some files must use this command.

@lunny
Copy link
Member

lunny commented Nov 16, 2024

Which git command did you execute to reproduce the problem?

@wxiaoguang
Copy link
Contributor

The root problem might be: "the LFS file is missing from server storage but the LFS record is still in database"

Usually, git lfs push only push changed files to the server, however:

  • Server thinks it has the file (the record is still in database)
  • But the file can't be accessed (the storage file is missing)
  • Server thinks the file exists and then git lfs push thinks the file is unchanged, so no real upload happens.

Then git lfs push --all origin makes (forces) git to push all LFS objects again to the server.

@Skodeva
Copy link
Author

Skodeva commented Nov 17, 2024

Which git command did you execute to reproduce the problem?

git push

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants