Re: Confusing git messages when disk is full.

From: Jeff King <peff@peff.net>
Date: Feb 15, 2017, 21:32 UTC
Message-ID: <20170215213221.lnraiktneokpk3mg@sigill.intra.peff.net>
In-Reply-To: <CABpqov=FE-h_2s=O9fkSjFjgFXSy6hDwc2fu5ijiVvkaLx9f_Q@mail.gmail.com>

On Sun, Feb 12, 2017 at 05:37:30PM +0100, Jáchym Barvínek wrote:

Show 6 quoted lines

> Hello, I would like to report what I consider a bug in git, I hope I'm
> doing it the right way.
> I was trying to run `git pull` in  my repository and got the following
> error: "git pull
> Your configuration specifies to merge with the ref 'refs/heads/master'
> from the remote, but no such ref was fetched."

It sounds like writing FETCH_HEAD failed, and git-pull became confused that the ref wasn't fetched.

Show 8 quoted lines

> Which was very confusing to me, I found some answers to what might be the cause
> but none was the right one. The actual cause was that the filesystem
> had no more free space.
> When I cleaned the space, `git pull` then gave the expected answer
> ("Already up-to-date.").
> I think the message is confusing and git should be able to report to
> the user that the cause
> is full disk.

If FETCH_HEAD failed to write because of a full disk (or any other reason), then the right thing is for "git fetch" to write an error to stderr, and git-pull should not continue the operation at all.

If we're not doing that, then that is certainly a bug.

-Peff