From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: Frequent git repository corruptions Date: Wed, 26 Sep 2018 12:50:30 +0200 Message-ID: <87r2hg5y89.fsf@elephly.net> References: <87lg7ofudd.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39020) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g57PY-0006cb-Nj for help-guix@gnu.org; Wed, 26 Sep 2018 06:51:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g57PV-0004Vs-HU for help-guix@gnu.org; Wed, 26 Sep 2018 06:51:16 -0400 Received: from sender-of-o51.zoho.com ([135.84.80.216]:21094) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1g57PV-0004VO-8G for help-guix@gnu.org; Wed, 26 Sep 2018 06:51:13 -0400 In-reply-to: <87lg7ofudd.fsf@ambrevar.xyz> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Pierre Neidhardt Cc: "help-guix@gnu.org" Pierre Neidhardt writes: > For the past 2-4 weeks I've had at least 4 Git repositories that got > corrupted for no apparent reason. Even a checkout that I had never > touched. > > When it happens, errors show up on most git commands, usually `git diff` > but sometimes also `git status`: > > --8<---------------cut here---------------start------------->8--- >> git diff > error: object file .git/objects/e0/1bd6c3c77309b13dab22f9e0de33576ede944f is empty > fatal: unable to read e01bd6c3c77309b13dab22f9e0de33576ede944f > --8<---------------cut here---------------end--------------->8--- > > A quick Internet search led me to realize there is little to do to > recover the corrupted repository beside cloning it again. I haven't > lost anything so far, knock on wood. > > My first thought was a hard drive issue. I have a NVMe SAMSUNG > MZVLW256HEHP. > I ran some smartmontools test, everything looks fine. Is the file system corrupt? (What does fsck say?) Did the system die without a proper shutdown? -- Ricardo