From: Junio C Hamano <gitster@pobox.com>
To: "R. Tyler Ballance" <tyler@slide.com>
Cc: git@vger.kernel.org
Subject: Re: Recovering from epic fail (deleted .git/objects/pack)
Date: Tue, 09 Dec 2008 16:19:50 -0800 [thread overview]
Message-ID: <7vd4g051ax.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1228867861.14165.19.camel@starfruit.local> (R. Tyler Ballance's message of "Tue, 09 Dec 2008 16:11:01 -0800")
"R. Tyler Ballance" <tyler@slide.com> writes:
> I really wish I didn't have to ask this question, as we discussed in
> #git early this morning, whiskey is the likely answer.
>
> For unexplainable reasons one of our sysadmins got trigger-happy when he
> tried to prune a temp_pack file generated and left in a
> developer's .git/ directory after a git operation aborted (disk quota
> exceeded)
>
> As a result, the sysadmin killed the developers
> entire .git/objects/pack/ directory. (insert copious amounts of whiskey
> here)
>
> He did not however delete all the other contents of .git/objects (00/,
> 01/, etc)
>
> Is there a feasible way that I can properly recover
> the .git/objects/pack directory such that the developer who had their
> last two weeks of local work thrashed can get it back?
I do not know about "feasible" and "properly", but ...
(0) take backup of the repository of this unfortunate developer.
(1) make a fresh clone of the central repository that this unfortunate
developer's work started out from.
(2) copy the contents of the .git/objects/pack/ of that clone to the
developer's .git/objects/pack/.
See if "fsck --full" complains after that. If the repository was not
repacked during that period, all objects created by the activity by the
unfortunate developer would be loose, so ...
next prev parent reply other threads:[~2008-12-10 0:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 0:11 Recovering from epic fail (deleted .git/objects/pack) R. Tyler Ballance
2008-12-10 0:19 ` Junio C Hamano [this message]
2008-12-10 10:06 ` R. Tyler Ballance
2008-12-10 11:39 ` Johannes Sixt
2008-12-10 22:52 ` epic fsck SIGSEGV! (was Recovering from epic fail (deleted .git/objects/pack)) R. Tyler Ballance
2008-12-10 23:40 ` Linus Torvalds
2008-12-11 0:24 ` R. Tyler Ballance
2008-12-11 0:45 ` Linus Torvalds
2008-12-11 1:21 ` R. Tyler Ballance
2008-12-11 0:51 ` epic fsck SIGSEGV! Junio C Hamano
2008-12-11 1:03 ` epic fsck SIGSEGV! (was Recovering from epic fail (deleted .git/objects/pack)) Boyd Stephen Smith Jr.
2008-12-11 1:16 ` Shawn O. Pearce
2008-12-11 1:33 ` Nicolas Pitre
2008-12-11 1:52 ` epic fsck SIGSEGV! Junio C Hamano
2008-12-11 2:16 ` Nicolas Pitre
2008-12-11 3:28 ` epic fsck SIGSEGV! (was Recovering from epic fail (deleted .git/objects/pack)) Linus Torvalds
2008-12-11 3:44 ` Linus Torvalds
2008-12-11 7:33 ` epic fsck SIGSEGV! Junio C Hamano
2008-12-11 17:33 ` Linus Torvalds
2008-12-11 20:18 ` Linus Torvalds
2008-12-11 7:53 ` Junio C Hamano
2008-12-11 4:00 ` epic fsck SIGSEGV! (was Recovering from epic fail (deleted .git/objects/pack)) Boyd Stephen Smith Jr.
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=7vd4g051ax.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=tyler@slide.com \
/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).