git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Problem with pack

From
SCSergio Callegari <scallegari@arces.unibo.it>
Date
Aug 25, 2006, 08:45 UTC
Message-ID
<44EEB8AD.5080703@arces.unibo.it>
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: Johannes Schindelin
Message 1 of 2 in “Problem with pack”
  1. Sergio CallegariAug 25, 2006
  2. Johannes SchindelinAug 25, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.