Git LFS Objects failing to delete after Repo Deletion on ADO

[noah-wolton]

Select Topic Area

Bug

Body

Hi,

I've communicated lots with Microsoft ADO support on this issue and my support agent said that it might be best to contact Git Support. I'm not sure this is the right avenue to do so, so please let me know if there is a better way to raise this issue. I realise ADO is not github enterprise, but I thought this might be the most relevant place to post this.

The issue comes from deleting a git repo with large LFS objects on an ADO Server. The repo has been deleted but the Git LFS objects have stuck around and every attempt to clean up these objects has failed. I've described the issue in this support ticket on the Microsoft forum and after communicating there to no success, I got a Microsoft support agent to communicate with. And while we have managed to find and fix one of the background cleanup tasks on ADO that was failing, the git LFS objects remain.

It has been ~ 2 months since their creation and they total some 180 GB. I understand this is an extremely complex and difficult issue to diagnose as it sits between the ADO and Git systems, but I would really appreciate and information or steps I could run to help diagnose and fix the issue.

Thanks in advance,
Noah

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐