Re: Remote corruption issue, linked to thin pack code?

From: Jonas Thiem <contact@eloxoph.com>
Date: Aug 26, 2010, 10:13 UTC
Message-ID: <4C763E30.2050407@eloxoph.com>
In-Reply-To: <alpine.LFD.2.00.1008252107070.622@xanadu.home>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi,

I'll try to provide the missing information as good as I can:

> What about 'git fsck --full'?  Given git v1.5.4 on the remote, you 
> should try --full with 'git fsck' as this wasn't the default back then.

$ GIT_DIR=./ git fsck --full dangling commit d298351127861349846fe626a320c66101821d72 dangling commit a71ea8dd4c837c39ef26765574d515253ea2fd5a

> What about 'git cat-file -t e28ae6b61c384732c506' ?

$ GIT_DIR=./ git cat-file -t e28ae6b61c384732c506 commit

> Also, what is the OS version and filesystem used on the remote machine?

OS is Ubuntu 8.04 LTS. It's a virtual server by a hosting company, therefore I don't know much about the filesystem setup, but maybe that helps:

$ df -T:
Filesystem    Type   1K-blocks      Used Available Use% Mounted on
/dev/vzfs reiserfs    10485760   4056808   6428952  39% /
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iF4EAREIAAYFAkx2Ph8ACgkQVizsUChSmww9TAEAptTyg+0yqidArbg2wMLmgac+ PrK9T3g4cU20EBOEuXkBALlqLapTQLlyO8UoFi+I3Mq64sDBBdjaEqH8bi6LcTor =ahRa -----END PGP SIGNATURE-----