From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: git clone dies (large git repository)
Date: Sat, 19 Aug 2006 12:58:22 +0200 [thread overview]
Message-ID: <ec6qsa$aal$2@sea.gmane.org> (raw)
In-Reply-To: op.teh30gmyies9li@rygel.lnxi.com
Troy Telford wrote:
> I originally had everything as loose objects. I then ran 'git-repack -d'
> on occasion, so I had a combination of a large pack file, smaller pack
> files, and loose objects. Finally, I tried 'git repack -a -d' and
> consolidated it all into a single 4GB pack file. It didn't seem to make
> much difference in the output.
>
> Am I bumping some sort of limitation within git, or have I uncovered
> a bug?
You _might_ have bumped into filesystem limit on file size, or system limit
on mmap size.
IIRC it was to be addressed (splitting packs into manageable hunks).
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-08-19 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 22:42 git clone dies (large git repository) Troy Telford
2006-08-19 10:58 ` Jakub Narebski [this message]
2006-08-19 20:46 ` Junio C Hamano
2006-08-21 23:30 ` Troy Telford
2006-08-22 0:23 ` Junio C Hamano
2006-08-22 0:42 ` Jakub Narebski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ec6qsa$aal$2@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).