From: Richard Weinberger <richard@nod.at>
To: git@vger.kernel.org
Cc: David Gstir <david@sigma-star.at>
Subject: broken repo after power cut
Date: Sat, 20 Jun 2015 21:40:38 +0200 [thread overview]
Message-ID: <5585C1B6.50407@nod.at> (raw)
Hi!
Yesterday our git server faced a power cut and a git repository broke.
The server is running a ext4 filesystem on top of Linux 3.16 (stable from openSUSE) and git 2.1.4.
We had a backup, so no data was lost but I really would like to figure out
what happened.
This is the output of git fsck:
Checking object directories: 100% (256/256), done.
error: object file objects/ce/f7627fc160ad7294b1f728db0c1ddb65a38b1d is empty
error: object file objects/ce/f7627fc160ad7294b1f728db0c1ddb65a38b1d is empty
fatal: loose object cef7627fc160ad7294b1f728db0c1ddb65a38b1d (stored in objects/ce/f7627fc160ad7294b1f728db0c1ddb65a38b1d) is corrupt
To me it seems like git was creating a new object and got interrupted before fsync/fdatasync'ing it.
As the object was referenced before syncing the data to disk the repo broke.
Could this have happened?
Also, is git designed to survive power cuts? Then referencing an object before synching it do disk would make no sense.
Thanks,
//richard
next reply other threads:[~2015-06-20 19:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-20 19:40 Richard Weinberger [this message]
2015-06-21 12:28 ` broken repo after power cut Johannes Schindelin
2015-06-21 13:07 ` Richard Weinberger
2015-06-21 13:59 ` Christoph Hellwig
2015-06-21 14:08 ` Richard Weinberger
2015-06-22 0:35 ` Theodore Ts'o
2015-06-22 11:19 ` Richard Weinberger
2015-06-22 12:31 ` Theodore Ts'o
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=5585C1B6.50407@nod.at \
--to=richard@nod.at \
--cc=david@sigma-star.at \
--cc=git@vger.kernel.org \
/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).