That's essentially the conclusion I've come to. I've had to restart my
repositories on the new memory limited remote.
That git clone ignores pack size, and that git is unable to handle large
files is just disappointing. I'm sure we've all had to wrote libraries to
parse files that are large then available memory for one reason or another
and found suitable ways to deal with it. GB data files are common enough,
at least in my line of work. For the time being I'll see how it goes
without adding another layer like git-annex, but I may have to look into it
in the future.
Thanks for your response Thomas

On Tue, Jul 24, 2012 at 2:34 PM, Thomas Ferris Nicolaisen
<tfn...@gmail.com>wrote:

> On Saturday, July 21, 2012 12:20:48 AM UTC+2, EJ Etherington wrote:
>>
>> Greetings,
>> I've been using git for a while but am fairly new to setting up a central
>> shared point like gitolite.
>> I am able to arbitrarily create small repository but have run into
>> trouble migrating existing repositories to gitolite. This seems entirely
>> due to a combination of two things. Very large individual files in the
>> history, binary and text files (such as mysql dumps), and the lack of swap
>> space on my inMotion VPS. The VPS should have 1G memory with about 700MB
>> free at any given time.
>>
>> When I create a new repository on the server and clone to my desktop all
>> is well. When I experimented with progressively larger file sizes, it
>> breaks unrecoverably (as far as I can tell) when I get to 1GB text file
>> sizes. Once I get to that size, I get out of memory errors when cloning and
>> bad pack errors when pushing.
>>
>> I have tried all manner of sizes for the pack.windowMemory, pack.threads,
>> pack.window, depth, deltaCacheSize packedGitWindowSize etc.
>> I have spent all of this past week researching and have found nothing
>> that helped.
>> Can anyone suggest something that, perhaps I have not tried?
>>
>
> I think the only thing you can do is to find some way to keep these huge
> files outside your repository. Adding files that are bigger than your
> available memory sounds like a really bad idea. Perhaps something like
> git-annex <http://git-annex.branchable.com/> could help.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/git-users/-/nDZacdmlExsJ.
>
> To post to this group, send email to git-users@googlegroups.com.
> To unsubscribe from this group, send email to
> git-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/git-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Reply via email to