Summary

Unexpected notes and v* (e.g. v0, v1, ..., v99) folders are present in the git repositories in Bitbucket Server.

These can cause the Bitbucket to stop attempting to run git garbage collection on the repositories and the following message being logged in the atlassian-bitbucket.log file:

Abandoning garbage collection after 3 failed attempts
com.atlassian.bitbucket.scm.CommandFailedException: '/bib/git/bin/git repack -A -d -l -n --unpack-unreachable=72.hours.ago' exited with code 128 saying: fatal: bad object refs/pull-requests/<pr_id>/v22

Steps to Reproduce

Unknown so far

Expected Results

No unexpected folders are present in the git repositories by Bitbucket Server.

Actual Results

Repositories contain unexpected folders:

• $BITBUCKET_HOME/data/repositories/<repository_id>/refs/pull-requests/notes
• $BITBUCKET_HOME/data/repositories/<repository_id>/refs/pull-requests/<pr_id>/v*

And the git garbage collection fails with the following message:

Abandoning garbage collection after 3 failed attempts
com.atlassian.bitbucket.scm.CommandFailedException: '/bib/git/bin/git repack -A -d -l -n --unpack-unreachable=72.hours.ago' exited with code 128 saying: fatal: bad object refs/pull-requests/<pr_id>/v22

Workaround

Reach out to Atlassian Support for assistance on how to manually remove the unexpected folders.