Web lists-archives.com

Re: fatal: unable to read after commit

Hash: SHA512

Hi Christian,

Am Fr den 12. Apr 2019 um  9:39 schrieb Christian Couder:
> On Thu, Apr 11, 2019 at 7:24 PM Klaus Ethgen <Klaus@xxxxxxxxx> wrote:
> > I am a heavy user of git now at version 2.20.1 on debian.
> >
> > Since some weeks I have the problem that I get often "fatal: unable to
> > read ..." and a unclear repository after a git commit. The commit itself
> > is correct and so a git reset --hard helps to fix the issue.
> Could you tell us at least which Debian version and file system you use?

Sorry, it is debian unstable and the filesystem is a brfs.

> Would you be ok to bisect it or at least tell us if it happens with
> 2.19.2, 2.20.0 and 2.21.0?

I could try, but from the fact, that it happens not all the time, I am
not sure if it helps.

However, I might have found one repo where it allways happens. In fact,
I am able to reproduce it also in my local geeqie checkout.

> > Any Idea what could be the reason for that problem. I encounter it on
> > different repositories so not limited to one.
> Is it easy to reproduce even on very small test repos? Could you send
> us a small script that reproduces it?

In any case it happens if I modify a file and add+commit or commit -a
it. What happens is that the index seems to be corrupted. The HEAD gets
the correct commit and the checked out version of the file is also
correct. Only the index seems to be corrupt (Until I do git reset).

When I do a git status, I get the following output:
   Auf Branch master
   Ihr Branch ist 1 Commit vor 'origin/master'.
     (benutzen Sie "git push", um lokale Commits zu publizieren)

   Zum Commit vorgemerkte Änderungen:
     (benutzen Sie "git reset HEAD <Datei>..." zum Entfernen aus der Staging-Area)

	   neue Datei:     pending.data

   Änderungen, die nicht zum Commit vorgemerkt sind:
     (benutzen Sie "git add/rm <Datei>...", um die Änderungen zum Commit vorzumerken)
     (benutzen Sie "git checkout -- <Datei>...", um die Änderungen im Arbeitsverzeichnis zu verwerfen)

	   gelöscht:       pending.data

And it seems, that the brocken object is always the same:
   > git diff
   fatal: unable to read 544f4ec5fe7c7b04c73b2c2fe9e3e7779e929819

independent from the repository.

I do not have a pending.data and did not touch this one.

> Could you also run the Git test suite on your machine?


But at the moment, I have some more findings that points to another
component in the queue. When I do a "commit -a -m test", the error does
not happens. When I do a "commit -a" and use the editor (vim) to write
the commit message, it happens.

As I use fugitive, I cannot rule out, that the problem is in that vim

- -- 
Klaus Ethgen                                       http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16            Klaus Ethgen <Klaus@xxxxxxxxx>
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
Comment: Charset: ISO-8859-1