> For example, if "du -sh" says 8.5GB, it doesn't necessarily mean that > there really is 8.5GB of data there. > Its very likely this did fit in just under 4 GiB of packed data, > but as you said, without O_LARGEFILE we can't work with it. .git is 3.5GB according to du -H :) > As Linus said earlier in this thread; Nico and I are working on > pushing out the packfile limits, just not fast enough for some users > needs apparently (sorry about that!). Troy's patch was rejected No problem. You're providing things to work around faster than I can process them :-) > So the "git repack" actually worked for you? It really shouldn't have > worked. It did not complain. I did not check the exit status but there were no so much as a single warning message: index file has overflown the kernel will panic shortly. please stand by... > Is the server side perhaps 64-bit? If so, the limit ends up being 4GB > instead of 2GB, and your 8.5GB project may actually fit. both server and client are 32 bit. > If so, we can trivially fix it with the current index file even for a > 32-bit machine. The reason we limit pack-files to 2GB on 32-bit machines Unfortunately the server machine is managed by IT. I can't install whatever I want. The client is not and it's against the IT policy to have rogue linux boxes on the net ;) > So, wouldn't the correct fix be to automatically split a pack > file in two pieces when it would become larger than 2 GB? Just curious why won't you use something like PostgreSQL for data storage at this point, but, then I know nothing about git internals :) Anyhow, I have a patch to apply now and a bash script to hone my bashing skills on. If you have anything else for me to test just shoot me an e-mail. I'm glad I can keep you all busy. ____________________________________________________________________________________ Expecting? Get great news right away with email Auto-Check. Try the Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html