Re: [Possible Bug] Commit generates GC repack failure

From: Duy Nguyen <pclouds@gmail.com>
Date: Jan 14, 2019, 15:07 UTC
Message-ID: <CACsJy8AtyTDs25R2PBd+nAvCW9aCYxtPHdXTS57JSS5VzgSFwQ@mail.gmail.com>
In-Reply-To: <CACsJy8AEi4gzRpHY+ehFz3GEOaQ0rmdC2kKMpUSp80cdQbuc6g@mail.gmail.com>

On Mon, Jan 14, 2019 at 10:03 PM Duy Nguyen <pclouds@gmail.com> wrote:

Show 22 quoted lines

>
> On Mon, Jan 14, 2019 at 9:51 PM Randall S. Becker
> <rsbecker@nexbridge.com> wrote:
> >
> > Hi All,
> >
> > I'm trying to track down what happened this morning. We had a commit that
> > caused a background gc to occur. What happened was:
> >
> > $ git commit -m "history commit ... "
> > Auto packing the repository in background for optimum performance.
> > See "git help gc" for manual housekeeping.
> > warning: The last gc run reported the following. Please correct the root
> > cause
> > and remove .git/gc.log.
> > Automatic cleanup will not be performed until the file is removed.
> >
> > fatal: open /dev/null failed: Invalid function argument
>
> sanitize_stdfds() in setup.c can attempt to open /dev/null then
> redirect stdout and stderr to it. I think this is part of the
> daemonization that is done in background gc.

However the message does not match. I think you will find this "open /dev/null failed" line in run-command.c

-- 
Duy