Re: Git chokes on large file

From: Dale R. Worley <worley@alum.mit.edu>
Date: May 28, 2014, 18:18 UTC
Message-ID: <201405281818.s4SIIV5n026003@hobgoblin.ariadne.com>
In-Reply-To: <xmqqbnuhesm5.fsf@gitster.dls.corp.google.com>

> From: Junio C Hamano <gitster@pobox.com>

> You need to have enough memory (virtual is fine if you have enough
> time) to do fsck.  Some part of index-pack could be refactored into
> a common helper function that could be called from fsck, but I think
> it would be a lot of work.

How much memory is "enough"? And how is it that fsck is coded so that the available RAM is a limit on which repositories can be checked? Did someone forget that RAM may be considerably smaller than the amount of data a program may have to deal with?

Dale

$ 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.