From: Rich <forums@artfulrobot.uk>
To: git@vger.kernel.org
Subject: Segfault during fsck and spreading brokenness
Date: Fri, 25 Sep 2020 16:48:39 +0100 [thread overview]
Message-ID: <2aa62ff7-0780-8e20-e87d-387152524971@artfulrobot.uk> (raw)
I was encouraged by a couple of people on stackoverflow to post to this
list. Apols in advance if it's not the right place.
I encountered a Segfault during fsck on a damaged bare repo (probably
due to a powercut. Possibly during an operation, although not sure):
git --version
git version 2.11.0
git fsck --full -v
Checking HEAD link
Checking object directory
Checking tree 11bbc847cf1b4422b3e37830a9eac2e7af6559de
Checking tree 11be4abeb20314de6145dfc0e6180807a74c03dc
--->8 snip 8<---------------------------------------------------------------
Checking tree 14a4423e86f06c7ad75bf391d138e0cf7790508f
Checking tree 147aeaec72b2f29bf1813494c942fbce497be679
zsh: segmentation fault git fsck --full -v
Host: Debian 10. Linux 4.9.0-13-amd64 #1 SMP Debian 4.9.228-1
(2020-07-05) x86_64 GNU/Linux
FS: BTRFS
I learnt about the damage while trying to `git push` from my dev
working tree. I think I did a `git pull` when the `git push` failed. The
result of this was that my *local* repo was also damaged: there was an
empty file created that would stop git operations and on deleting that I
got a page full of errors.
Original SO question:
https://stackoverflow.com/questions/64044995/can-one-corrupt-git-repo-corrupt-another?noredirect=1
Unfortunately I don't think I'm at liberty to give access to the repo as
it possibly contains sensitive info/personal data.
I have solved the problem for myself (took a morning to do it!) but
reporting here in case it's useful to do so. I use git all the time and
I'm grateful for it. I'm not a systems-level coder, so not sure what use
I'll be, but happy to answer any Qs or try things on the broken copies.
Thanks,
Rich
next reply other threads:[~2020-09-25 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 15:48 Rich [this message]
2020-09-25 17:47 ` Segfault during fsck and spreading brokenness Jeff King
2020-09-28 6:43 ` Rich
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2aa62ff7-0780-8e20-e87d-387152524971@artfulrobot.uk \
--to=forums@artfulrobot.uk \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).