From: Jonas Thiem <contact@eloxoph.com>
To: Nicolas Pitre <nico@fluxnic.net>, git@vger.kernel.org
Subject: Re: Remote corruption issue, linked to thin pack code?
Date: Thu, 26 Aug 2010 12:13:04 +0200 [thread overview]
Message-ID: <4C763E30.2050407@eloxoph.com> (raw)
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-----
prev parent reply other threads:[~2010-08-26 10:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 20:53 Remote corruption issue, linked to thin pack code? Thomas Rast
2010-08-26 2:42 ` Nicolas Pitre
2010-08-26 7:13 ` Thomas Rast
2010-08-26 10:13 ` Jonas Thiem [this message]
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=4C763E30.2050407@eloxoph.com \
--to=contact@eloxoph.com \
--cc=git@vger.kernel.org \
--cc=nico@fluxnic.net \
/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).