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

multi-pack-index expiration ineffective due to many pack-files keeping small object counts #676

Closed
2 tasks done
derrickstolee opened this issue Jul 15, 2024 · 4 comments
Closed
2 tasks done
Assignees

Comments

@derrickstolee
Copy link
Collaborator

When exploring my .scalarCache for the Office monorepo, I saw many prefetch pack-files that had not been deleted by routine maintenance. I ran and reran git maintenance run --task=incremental-repack expecting old pack-files to be deleted. However, the old pack-files are not being removed.

I added some trace2 statements to the expiration code and found that these pack-files still have a number of objects (sometimes as low as 2 or 3, but other times in the hundreds or thousands) reference by the multi-pack-index.

The root cause is likely a problem with the git multi-pack-index repack process instead of the expire operation. I may investigate this later, but need to make a note now before I forget.

  • If the problem was occurring with a specific repository, can you specify
    the repository?

    • Office monorepo
@derrickstolee derrickstolee self-assigned this Jul 16, 2024
@derrickstolee
Copy link
Collaborator Author

This is new behavior in 2.45.0 and due to b7d6f23. I intend to revert this in microsoft/git before 2.46.0.vfs.0.0 but will investigate more deeply for an upstream fix.

@dscho
Copy link
Member

dscho commented Jul 16, 2024

@derrickstolee now that you fixed this in #678, shall we close this ticket? Or do you want to wait until there is an official release with the work-around?

@derrickstolee
Copy link
Collaborator Author

@dscho I have an internal ticket to track the upstreaming of this change, so we can close this. Thanks for your help!

Copy link
Member

dscho commented Jul 17, 2024

Great, thank you for letting me know!

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

No branches or pull requests

2 participants