From: Taylor Blau <me@ttaylorr.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: git@vger.kernel.org
Subject: Re: Repository corruption if objects pushed in the middle of repack
Date: Mon, 13 Jun 2022 17:18:25 -0400 [thread overview]
Message-ID: <YqepoUMb3rkKgWqB@nand.local> (raw)
In-Reply-To: <20220613203145.wbpi2m3ys3hchw6c@meerkat.local>
Hi Konstantin,
On Mon, Jun 13, 2022 at 04:31:45PM -0400, Konstantin Ryabitsev wrote:
> As far as I know, the maintenance steps we are running shouldn't result in any
> missing objects, so I'm curious if it's something we're doing wrong (using
> unsafe flags) or if git isn't properly accounting for some objects that come
> in during the repack stage. We're seeing this happen fairly routinely, so it's
> not just a random fluke.
Interesting. From what you described, it does suggest that `repack` is
deleting things too eagerly.
But I would be quite surprised if that were the case, since `repack` is
*very* careful to only delete packs which it knew about at the start of
the repack. Likewise, when it cleans up loose objects, it only unlinks
objects which can be found in some (non-deleted) pack that will remain
in the repository.
So I doubt that repack is doing something weird here, though it would be
extremely interseting if you were able to pause the `repack` process at
a specific point, push new objects into the repository, and reliably
demonstrate the corruption.
Thanks,
Taylor
next prev parent reply other threads:[~2022-06-13 21:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 20:31 Repository corruption if objects pushed in the middle of repack Konstantin Ryabitsev
2022-06-13 21:18 ` Taylor Blau [this message]
2022-06-13 21:24 ` Taylor Blau
2022-06-13 21:32 ` Konstantin Ryabitsev
2022-06-13 21:36 ` Taylor Blau
2022-06-13 21:45 ` Konstantin Ryabitsev
2022-06-13 22:26 ` Chris Torek
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YqepoUMb3rkKgWqB@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=konstantin@linuxfoundation.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox