From: Thomas Rast <trast@inf•ethz.ch>
To: Sivaram Kannan <siva.devel@gmail•com>
Cc: Duy Nguyen <pclouds@gmail•com>,
Konstantin Khomoutov <flatworm@users•sourceforge.net>,
git <git@vger•kernel.org>
Subject: Re: Git crash in Ubuntu 12.04
Date: Fri, 19 Apr 2013 09:53:29 +0200 [thread overview]
Message-ID: <87zjwvt0qu.fsf@linux-k42r.v.cablecom.net> (raw)
In-Reply-To: <CAJiNi_HA5bNO8gMHkts_e+dWG26n=S7MRF5wc_L+v=rbnM91oQ@mail.gmail.com> (Sivaram Kannan's message of "Thu, 18 Apr 2013 20:46:45 +0530")
Sivaram Kannan <siva.devel@gmail•com> writes:
> Hi,
>
> The git crashed during one of the commits by a developer I think, the
> remote is not even showing the working branch. The local branch of is
> all right, but the remote repo is corrupted and could not git fsck
> also. Is restoring the last night's backup is my only option??
By commit, do you mean push? I.e., something crashed while a push was
going on?
The recovery strategy depends a lot on how valuable/recoverable the work
that happened since the last backup was, but restoring from backup,
running 'git fsck' on all involved repos (including devs' workstations!)
and then having the devs re-push what they had locally seems like a good
strategy to me.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2013-04-19 7:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 6:41 Git crash in Ubuntu 12.04 Sivaram Kannan
2013-04-10 7:44 ` Thomas Rast
2013-04-11 10:20 ` Sivaram Kannan
2013-04-11 13:06 ` Konstantin Khomoutov
2013-04-12 13:28 ` Sivaram Kannan
2013-04-12 14:05 ` Konstantin Khomoutov
2013-04-17 6:28 ` Sivaram Kannan
2013-04-17 7:26 ` Duy Nguyen
2013-04-18 11:32 ` Sivaram Kannan
2013-04-18 15:16 ` Sivaram Kannan
2013-04-19 7:53 ` Thomas Rast [this message]
2013-04-19 8:48 ` Duy Nguyen
2013-04-24 14:51 ` Sivaram Kannan
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=87zjwvt0qu.fsf@linux-k42r.v.cablecom.net \
--to=trast@inf$(echo .)ethz.ch \
--cc=flatworm@users$(echo .)sourceforge.net \
--cc=git@vger$(echo .)kernel.org \
--cc=pclouds@gmail$(echo .)com \
--cc=siva.devel@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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