user/dev discussion of public-inbox itself
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@mellanox.com>
To: "meta@public-inbox.org" <meta@public-inbox.org>
Subject: error: failed to run repack
Date: Tue, 11 Jun 2019 11:39:10 +0000
Message-ID: <DB6PR0501MB216765FD2F9EA337FD0E6A41D7ED0@DB6PR0501MB2167.eurprd05.prod.outlook.com> (raw)

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)
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?

Thanks,
Ali

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 11:39 Ali Alnubani [this message]
2019-06-11 19:24 ` Eric Wong
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://public-inbox.org/README

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

  git send-email \
    --in-reply-to=DB6PR0501MB216765FD2F9EA337FD0E6A41D7ED0@DB6PR0501MB2167.eurprd05.prod.outlook.com \
    --to=alialnu@mellanox.com \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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 http://public-inbox.org/meta
	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/ http://public-inbox.org/meta \
		meta@public-inbox.org
	public-inbox-index meta

Example config snippet for mirrors.
Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta
	nntp://ou63pmih66umazou.onion/inbox.comp.mail.public-inbox.meta
	nntp://czquwvybam4bgbro.onion/inbox.comp.mail.public-inbox.meta
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.mail.public-inbox.meta
	nntp://news.gmane.io/gmane.mail.public-inbox.general
 note: .onion URLs require Tor: https://www.torproject.org/

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

	https://80x24.org/public-inbox.git

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git