Skip to content

Need documentation for repository repair or way to actually force a push #2193

@allaryin

Description

@allaryin

I have a client with a 30gb repository stored primarily in LFS (via GitLab). If I do a fetch --all, I get 30 gigs of files, plus 404's on 6 of them. But the 6 problematic files all exist on disk and contain valid data - so I am assuming that these 404's are merely for ancient historical versions of the files.

I need to create a full mirror of the repository, but cannot because git bails with "LFS upload failed" on the six files in question (after having successfully uploaded the other 30gb of data to our server).

After fighting this issue for several days, upgrading git-lfs to 2.1.0, and continuing to fight it for two more, I am at a loss. I cannot find any comprehensive documentation on how to simply make this push happen so I can move on to actually using the data. I don't care about losing a little history, just as long as the bulk remains intact.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions