user/dev discussion of public-inbox itself
 help / color / mirror / Atom feed
From: Eric Wong <>
To: Ali Alnubani <>
Subject: Re: error: failed to run repack
Date: Tue, 11 Jun 2019 19:24:43 +0000
Message-ID: <20190611192443.opg3afru6tfueabr@dcvr> (raw)
In-Reply-To: <>

Ali Alnubani <> wrote:
> Hi,
> I keep seeing the following in my logs for multiple lists:
> timestamp public-inbox-watch[PID]: Auto packing the repository in background for optimum performance.
> timestamp public-inbox-watch[PID]: See "git help gc" for manual housekeeping.
> timestamp public-inbox-watch[PID]: error: The last gc run reported the following. Please correct the root cause
> timestamp public-inbox-watch[PID]: and remove path/to/repo.git/git/0.git/gc.log.
> timestamp public-inbox-watch[PID]: Automatic cleanup will not be performed until the file is removed.
> timestamp public-inbox-watch[PID]: fatal: Failed to write bitmap index. Packfile doesn't have full closure (object 817390f628f74a55c627f1ddab8a44aa029753a0 is missing)

Do you have a path/to/repo.git/git/0.git/objects/info/alternates ?

Bitmaps won't work when packing a repo with alternates
In other words, does 817390f628f74a55c627f1ddab8a44aa029753a0
exist in your 0.git, or somewhere else?

The normal epoch repos (git/[0-9]+.git) aren't created with alternates
by default; instead all.git uses git/[0-9]+.git as alternates.

> timestamp public-inbox-watch[PID]: error: failed to run repack
> Running 'git-fsck -full' in path/to/repo.git/git/0.git doesn't report any issues.
> I imported my archives using scripts/import_vger_from_mbox.
> Any clue? Also is it safe to attempt a manual git-gc?

You might have the same result.  You can probably disable bitmaps
in all.git/config and set it in a git repo that does have full

  reply	other threads:[~2019-06-11 19:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 11:39 Ali Alnubani
2019-06-11 19:24 ` Eric Wong [this message]
2019-06-12 13:05   ` Ali Alnubani
2019-06-12 17:02     ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190611192443.opg3afru6tfueabr@dcvr \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

user/dev discussion of public-inbox itself

This inbox may be cloned and mirrored by anyone:

	git clone --mirror
	git clone --mirror http://czquwvybam4bgbro.onion/meta
	git clone --mirror http://hjrcffqmbrq6wope.onion/meta
	git clone --mirror http://ou63pmih66umazou.onion/meta

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 meta meta/ \
	public-inbox-index meta

Example config snippet for mirrors.
Newsgroups are available over NNTP:
 note: .onion URLs require Tor:

code repositories for the project(s) associated with this inbox:

AGPL code for this site: git clone