Re: Large pack causes git clone failures ... what to do?
- From
Geoff Russell <geoffrey.russell@gmail.com>
- Date
- Sep 1, 2010, 01:53 UTC
- Message-ID
- <AANLkTik2Ms6qjQAaa_H8GGwmTG1fsk+8GR2y7ZmLviY-@mail.gmail.com>
- In-Reply-To
- <AANLkTi=O5SbLRttzR0YwrHVEMz5gxtdTo9Z5C6V1yE1e@mail.gmail.com>
On Wed, Sep 1, 2010 at 7:33 AM, Geoff Russell <geoffrey.russell@gmail.com> wrote:
Show 12 quoted lines
> Thanks Shawn, > >... >> You really needed to run: >> >> git repack --max-pack-size=.. -a -d >> >> The -d flag tells it to remove the old packs once the new packs >> are ready, and the -a flag tells it to reconsider every object >> in the repository, rather than just those that are loose. > > Ok, will try.
The repack failed with a "fatal: Out of memory, malloc failed", perhaps I just need to try a machine with more memory!
I'm still interested in whether clone from a client take note of the pack.packSizeLimit if I set it on the server? Or does it use the client value?
Cheers, Geoff