From: Sergio Callegari <scallegari@arces.unibo.it>
To: git@vger.kernel.org
Subject: Problem with pack
Date: Fri, 25 Aug 2006 10:45:33 +0200 [thread overview]
Message-ID: <44EEB8AD.5080703@arces.unibo.it> (raw)
Hi,
I am encountering a problem after a
git repack -a -d
on an archive.
The packet that has been generated appears to be corrupted:
git verify-pack -v pack-ebcdfbbda07e5a3e4136aa1f499990b35685bab4.idx
fatal: failed to read delta-pack base object
2849bd2bd8a76bbca37df2a4c8e8b990811d01a7
and apparently I might have lost all the history of my project.
I have a few questions:
1) I am working on both a pc and a notebook, syncing the two everytime I
move from one to the other.
On the PC I have git 1.4.2, on the notebook git 1.4.0. I am using
"unison" as a syncing tool.
Might the data loss have something to do with...
- the version of git I am using or the mixing of two versions?
- the syncing? I have noticed that after a sync, git is not immediately
in a happy state... for instance if I run
git diff
git lists diff commands for every file, even if those have not changed.
However after a
git status
everything seems fine again.
2) git unpack-objects seems to be able to extract some objects from the
pack, but at a certain point it dies.
- does it die on the first error or does it try to extract everything
that is possible to extract after the error?
- if it's the first, is there a way to trigger the second behaviour to
try to save as much as possible from the pack?
Thanks,
Sergio Callegari
next reply other threads:[~2006-08-25 8:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-25 8:45 Sergio Callegari [this message]
2006-08-25 9:12 ` Problem with pack Johannes Schindelin
-- strict thread matches above, loose matches on Subject: below --
2006-08-25 10:07 Sergio Callegari
2006-08-25 10:20 ` Andreas Ericsson
2006-08-25 10:41 ` Jakub Narebski
2006-08-25 10:58 ` Junio C Hamano
2006-08-26 10:09 ` Junio C Hamano
2006-08-26 10:31 ` Junio C Hamano
2006-08-25 12:31 Sergio Callegari
2006-08-26 18:20 ` Linus Torvalds
2006-08-26 18:49 Sergio Callegari
2006-08-26 18:53 Sergio Callegari
2006-08-26 19:24 ` Linus Torvalds
2006-08-27 17:45 Sergio Callegari
2006-08-27 18:27 ` Linus Torvalds
2006-08-27 19:26 ` Nicolas Pitre
2006-08-27 21:55 ` Junio C Hamano
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=44EEB8AD.5080703@arces.unibo.it \
--to=scallegari@arces.unibo.it \
--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).