From: "Shawn O. Pearce" <spearce@spearce.org>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: fact-import: failed to apply delta
Date: Tue, 10 Feb 2009 13:25:39 -0800 [thread overview]
Message-ID: <20090210212539.GV30949@spearce.org> (raw)
In-Reply-To: <alpine.LNX.1.00.0902101520240.19665@iabervon.org>
Daniel Barkalow <barkalow@iabervon.org> wrote:
>
> I think maybe there's aliasing in the delta base cache? If it recycled a
> struct packed_git, the cache would come up with a cached tree at offset 12
> of the packed_git at that address, but the pack used by that struct has
> changed.
Yup, that must be it.
> I don't see any reason that the situation couldn't arise where you start a
> pack, look up an object in it while it's still open but the object isn't
> in the window, cache the delta base, end that packfile, eventually start a
> packfile that gets allocated in the space that was freed, produce a new
> delta against the object at exactly the same offset of the new pack (with
> the same address as the old pack), and go on happily until you try looking
> up this last delta and pull the wrong base out of the cache.
>
> I don't see any code to flush the delta cache ever, but it's hard to get a
> new packed_git allocated at the address of a freed one, except by doing a
> lot of checkpoints in fast-import...
*ouch*. I think you found it.
We should dump the cached_objects table in sha1_file.c during
a checkpoint in fast-import.
--
Shawn.
next prev parent reply other threads:[~2009-02-10 21:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 3:26 fact-import: failed to apply delta Daniel Barkalow
2009-02-10 10:28 ` Johannes Schindelin
2009-02-10 15:56 ` Shawn O. Pearce
2009-02-10 17:15 ` Daniel Barkalow
2009-02-10 17:22 ` Shawn O. Pearce
2009-02-10 17:47 ` Daniel Barkalow
2009-02-10 19:12 ` Shawn O. Pearce
2009-02-10 20:03 ` Daniel Barkalow
2009-02-10 20:12 ` Shawn O. Pearce
2009-02-10 21:19 ` Daniel Barkalow
2009-02-10 21:25 ` Shawn O. Pearce [this message]
2009-02-10 21:32 ` Daniel Barkalow
2009-02-10 21:36 ` Shawn O. Pearce
2009-02-10 21:51 ` Daniel Barkalow
2009-02-10 22:30 ` Junio C Hamano
2009-02-10 22:47 ` Junio C Hamano
2009-02-10 23:09 ` Shawn O. Pearce
2009-02-10 23:15 ` Junio C Hamano
2009-02-10 23:16 ` Shawn O. Pearce
2009-02-10 23:32 ` Junio C Hamano
2009-02-11 18:09 ` Daniel Barkalow
2009-02-11 18:15 ` Shawn O. Pearce
2009-02-11 18:30 ` Junio C Hamano
2009-02-11 18:33 ` Daniel Barkalow
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=20090210212539.GV30949@spearce.org \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).