git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Support empty blob in fsck --lost-found

From
Sverre Rabbelier <srabbelier@gmail.com>
Date
Sep 11, 2011, 16:03 UTC
Message-ID
<CAGdFq_hqfqdFyLY=KdA_QW5kH8Kjhx8Y18mHEga_Pdv8yzB2wg@mail.gmail.com>
In-Reply-To
<A3964281-B24B-46C0-AE73-0CCB4C12556F@bjhargrave.com>
Heya,
On Sun, Sep 11, 2011 at 17:40, BJ Hargrave <bj@bjhargrave.com> wrote:
> fsck --lost-found died when attempting to write out the empty blob.
> Avoid calling fwrite when the blob size is zero since the call to
> fwrite returns 0 objects written which fails the check and caused
> fsck to die.

Now we don't die at all if a 0-byte file couldn't be written. Shouldn't we check errno or something?

-- 
Cheers,

Sverre Rabbelier
Previous: BJ HargraveNext: BJ Hargrave
Message 2 of 7 in “Support empty blob in fsck --lost-found”
  1. Support empty blob in fsck --lost-foundBJ Hargrave, Sep 11, 2011
  2. Sverre RabbelierSep 11, 2011
  3. BJ HargraveSep 11, 2011
  4. Sverre RabbelierSep 11, 2011
  5. Junio C HamanoSep 11, 2011
  6. BJ HargraveSep 11, 2011
  7. Junio C HamanoSep 12, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.