Pierre Neidhardt <m...@ambrevar.xyz> 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
