git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@cam.org>
To: bob <kranki@mac.com>
Cc: git@vger.kernel.org
Subject: Re: git packs
Date: Sun, 11 Nov 2007 23:21:58 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.0.9999.0711112307070.21255@xanadu.home> (raw)
In-Reply-To: <B298202C-3D54-498D-A348-0338914FBA46@mac.com>

On Sun, 11 Nov 2007, bob wrote:

> I applied the patch and these commands:
> 
> cd rmwHtmlOld
> rm -fr .git
> git init
> git config core.compression 0
> git add .

Note that I did "git config core.compression 0" simply to disable 
zlib compression altogether when creating the test repo just so it gets 
created faster.  even then, auto-generating and cloning a 8GB test 
repository isn't particularly quick.

> I then got the same error as before, "Bus error".  Rats!

Do you get that with a 32-bit or 64-bit build of Git?

> Then I modified your script since I do not have seq or
> your test-genrandom.

test-genrandom is built with Git.  It is just not installed anywhere.

> I substituted:
> 
> dd count=XX  if=/dev/random of=file_$i
> 
> where XX is adjusted to meet dd's requirements.  Also,

Again I used test-genrandom instead of /dev/random or /dev/urandom 
simply because the former is much faster.

> I found after searching for a while, that the following
> works just like your seq command:
> 
> xyzzy="1 2 3 4"
> for i in $xyzzy
> do
> ...
> done
> 
> Your script then ran flawlessly.

However 'seq -w 1 2 63' should be replaced  with "01 03 05 07 09 11 13 
15" and so on up to 63, and 'seq -w 2 2 64' is "02 04 06 08 10 12 16" 
and so on.

> I looked through index-pack.c some more, but it is
> very hard to figure it out without doing a lot of research
> since there doesn't seem to be anything that describes
> the layout of a pack.  The link towards the end of the user's
> manual doesn't work for me.

Look at Documentation/technical/pack-format.txt in the Git source tree.

> The difference between your test and my data is that
> instead of having a few large files, I have 11,500 files
> of varying sizes.  On average though, the file size is
> about 370k.

Are you saying that the test repo with big files works for you but not 
your own data set?

Would you please recap what your problem is?

With my one line patch you should not get the "serious inflate 
inconsistency" error anymore.  The bus error must be another issue.


Nicolas

  reply	other threads:[~2007-11-12  4:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-10  4:47 git packs bob
2007-11-10  5:13 ` Nicolas Pitre
2007-11-10  6:00   ` bob
2007-11-10  6:36     ` Luke Lu
2007-11-10  6:58       ` Linus Torvalds
2007-11-10  7:59         ` David Brown
2007-11-10  6:38     ` Linus Torvalds
2007-11-10  6:53       ` Linus Torvalds
2007-11-10  7:19       ` bob
2007-11-11  4:35         ` Nicolas Pitre
2007-11-12  2:53           ` bob
2007-11-12  4:21             ` Nicolas Pitre [this message]
2007-11-12 14:15               ` bob
2007-11-10 17:40 ` bob
2007-11-10 17:45   ` David Brown
2007-11-10 18:01     ` bob
2007-11-11 11:09       ` Derek Fawcus
2007-11-11 12:54         ` bob
2007-11-12  4:46   ` Martin Langhoff

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=alpine.LFD.0.9999.0711112307070.21255@xanadu.home \
    --to=nico@cam.org \
    --cc=git@vger.kernel.org \
    --cc=kranki@mac.com \
    /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).