Thread: Errors when trying to use git.postgresql
walk 0d32db956dd3eaf0fc1aa4c3441e6255634c5a73 walk 808c935bf2a92a6363c31f3d0f2a8e5a00ac41d8 error: packfile .git/objects/pack/pack-f1126b29766ca414335d86fe7cbb91f44122e263.pack cannot be accessed error: packfile .git/objects/pack/pack-f1126b29766ca414335d86fe7cbb91f44122e263.pack cannot be accessed error: Couldn't create temporary file .git/objects/7f/a3d70b8bdbf8a0aa4b8ba5def7af5263f9294d.temp for .git/objects/7f/a3d70b8bdbf8a0aa4b8ba5def7af5263f9294d: Too many open files walk a00a9e5670bd337cae777aaa0c675f9a7e4ac9b4 walk 60f4177c107530773931919b2978f9362ea324af walk 483f816264dac02035cdaae7a81755c28de43127 walk 0bf15e49ccf77d7c9a80c584310d308284278ca9 walk 0b4d72490b449230bebc5e8c070fb998742a32ad walk 58cb526d59f65fd0f0595aa58dab88122b778d9f walk 8040c3add3ab7fa56ab6654f60952ba77fecb4a1 walk f583b7c4bc3dbd5b4d5fa78711f6a0f8ce446be1 walk 5ae6b17a685cb25da3c4301223515c825dbbe7f6 walk ecbe1b3135abb7d56de7ec7c12e54ceabef76608 walk 6ad3c6ca95d4c6f8bdc9a2be749ad50c293a5d26 walk 951dcd703dc7f8f709b3800f70d3f2e0c3129360 walk 5e3f27e9667b3548fd305ecd5a24d92a6906ffdb walk 73511928ad1dd30771799aa438dac16321726c04 walk a9d56ce6e952ad529118cc8aa923310b24ae95a6 walk 19c9088190ed3493de2676c34267b44b79c59ab3 walk 4ab5ae1b9a8f3258ca36862892c31cace4a4532d walk 008c6af33d45f03b24f9fa918b47d7975b08b076 error: packfile .git/objects/pack/pack-f1126b29766ca414335d86fe7cbb91f44122e263.pack cannot be accessed error: Request for 7fa3d70b8bdbf8a0aa4b8ba5def7af5263f9294d aborted Getting pack list for http://git.postgresql.org/git/postgresql.git Segmentation fault -- PostgreSQL Consulting, Development, Support, Training 503-667-4564 - http://www.commandprompt.com/ The PostgreSQL Company,serving since 1997
On Tue, Jan 13, 2009 at 1:58 PM, Joshua D. Drake <jd@commandprompt.com> wrote: > walk 0d32db956dd3eaf0fc1aa4c3441e6255634c5a73 > walk 808c935bf2a92a6363c31f3d0f2a8e5a00ac41d8 > error: > packfile .git/objects/pack/pack-f1126b29766ca414335d86fe7cbb91f44122e263.pack cannot be accessed > error: > packfile .git/objects/pack/pack-f1126b29766ca414335d86fe7cbb91f44122e263.pack cannot be accessed > error: Couldn't create temporary > file .git/objects/7f/a3d70b8bdbf8a0aa4b8ba5def7af5263f9294d.temp > for .git/objects/7f/a3d70b8bdbf8a0aa4b8ba5def7af5263f9294d: Too many > open files > walk a00a9e5670bd337cae777aaa0c675f9a7e4ac9b4 > walk 60f4177c107530773931919b2978f9362ea324af > walk 483f816264dac02035cdaae7a81755c28de43127 > walk 0bf15e49ccf77d7c9a80c584310d308284278ca9 > walk 0b4d72490b449230bebc5e8c070fb998742a32ad > walk 58cb526d59f65fd0f0595aa58dab88122b778d9f > walk 8040c3add3ab7fa56ab6654f60952ba77fecb4a1 > walk f583b7c4bc3dbd5b4d5fa78711f6a0f8ce446be1 > walk 5ae6b17a685cb25da3c4301223515c825dbbe7f6 > walk ecbe1b3135abb7d56de7ec7c12e54ceabef76608 Until something is done about the git.postgresql.org repo, I have a mirror (which you can validate via sha1 comparison/git fsck) at http://fdr.lolrus.org/postgresql.git/ There's another thread ("PostgreSQL GIT mirror status") where the problems have been discussed. AFAIK someone should be poised to fix up the main repository, but it hasn't happened yet. fdr
On Tue, 2009-01-13 at 15:47 -0800, Daniel Farina wrote: > On Tue, Jan 13, 2009 at 1:58 PM, Joshua D. Drake <jd@commandprompt.com> wrote: > > walk 0d32db956dd3eaf0fc1aa4c3441e6255634c5a73 > > walk 808c935bf2a92a6363c31f3d0f2a8e5a00ac41d8 > > error: > > packfile .git/objects/pack/pack-f1126b29766ca414335d86fe7cbb91f44122e263.pack cannot be accessed > > error: > > packfile .git/objects/pack/pack-f1126b29766ca414335d86fe7cbb91f44122e263.pack cannot be accessed > > error: Couldn't create temporary > > file .git/objects/7f/a3d70b8bdbf8a0aa4b8ba5def7af5263f9294d.temp > > for .git/objects/7f/a3d70b8bdbf8a0aa4b8ba5def7af5263f9294d: Too many > > open files > > walk a00a9e5670bd337cae777aaa0c675f9a7e4ac9b4 > > walk 60f4177c107530773931919b2978f9362ea324af > > walk 483f816264dac02035cdaae7a81755c28de43127 > > walk 0bf15e49ccf77d7c9a80c584310d308284278ca9 > > walk 0b4d72490b449230bebc5e8c070fb998742a32ad > > walk 58cb526d59f65fd0f0595aa58dab88122b778d9f > > walk 8040c3add3ab7fa56ab6654f60952ba77fecb4a1 > > walk f583b7c4bc3dbd5b4d5fa78711f6a0f8ce446be1 > > walk 5ae6b17a685cb25da3c4301223515c825dbbe7f6 > > walk ecbe1b3135abb7d56de7ec7c12e54ceabef76608 > > Until something is done about the git.postgresql.org repo, I have a > mirror (which you can validate via sha1 comparison/git fsck) at > http://fdr.lolrus.org/postgresql.git/ > > There's another thread ("PostgreSQL GIT mirror status") where the > problems have been discussed. AFAIK someone should be poised to fix up > the main repository, but it hasn't happened yet. Thanks for this. Trying it now. Joshua D. Drake > > fdr > -- PostgreSQL Consulting, Development, Support, Training 503-667-4564 - http://www.commandprompt.com/ The PostgreSQL Company,serving since 1997
On Tue, Jan 13, 2009 at 9:58 PM, Joshua D. Drake <jd@commandprompt.com> wrote: > walk 0d32db956dd3eaf0fc1aa4c3441e6255634c5a73 > walk 808c935bf2a92a6363c31f3d0f2a8e5a00ac41d8 > error: > packfile .git/objects/pack/pack-f1126b29766ca414335d86fe7cbb91f44122e263.pack cannot be accessed > error: > packfile .git/objects/pack/pack-f1126b29766ca414335d86fe7cbb91f44122e263.pack cannot be accessed > error: Couldn't create temporary > file .git/objects/7f/a3d70b8bdbf8a0aa4b8ba5def7af5263f9294d.temp > for .git/objects/7f/a3d70b8bdbf8a0aa4b8ba5def7af5263f9294d: Too many > open files > walk a00a9e5670bd337cae777aaa0c675f9a7e4ac9b4 > walk 60f4177c107530773931919b2978f9362ea324af > walk 483f816264dac02035cdaae7a81755c28de43127 > walk 0bf15e49ccf77d7c9a80c584310d308284278ca9 > walk 0b4d72490b449230bebc5e8c070fb998742a32ad > walk 58cb526d59f65fd0f0595aa58dab88122b778d9f > walk 8040c3add3ab7fa56ab6654f60952ba77fecb4a1 > walk f583b7c4bc3dbd5b4d5fa78711f6a0f8ce446be1 > walk 5ae6b17a685cb25da3c4301223515c825dbbe7f6 > walk ecbe1b3135abb7d56de7ec7c12e54ceabef76608 > walk 6ad3c6ca95d4c6f8bdc9a2be749ad50c293a5d26 > walk 951dcd703dc7f8f709b3800f70d3f2e0c3129360 > walk 5e3f27e9667b3548fd305ecd5a24d92a6906ffdb > walk 73511928ad1dd30771799aa438dac16321726c04 > walk a9d56ce6e952ad529118cc8aa923310b24ae95a6 > walk 19c9088190ed3493de2676c34267b44b79c59ab3 > walk 4ab5ae1b9a8f3258ca36862892c31cace4a4532d > walk 008c6af33d45f03b24f9fa918b47d7975b08b076 > error: > packfile .git/objects/pack/pack-f1126b29766ca414335d86fe7cbb91f44122e263.pack cannot be accessed > error: Request for 7fa3d70b8bdbf8a0aa4b8ba5def7af5263f9294d aborted > Getting pack list for http://git.postgresql.org/git/postgresql.git > Segmentation fault This happens on the local machine presumably? I used to suffer that problem and resolved it with 'ulimit -n 1024' in my bash profile. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
On Wed, Jan 14, 2009 at 12:58 AM, Dave Page <dpage@pgadmin.org> wrote: > This happens on the local machine presumably? I used to suffer that > problem and resolved it with 'ulimit -n 1024' in my bash profile. This is because the number of packs in the git.postgresql.org repo is enormous, which also slows down clones and many other git operations. Try running "git gc --aggressive" to fix this on your local copy (this will take a while -- probably hours -- unless you've done it before). On the other hand, I've recorded a size difference in the pack going from > 300 MB to ~100MB. Using a fresh clone from git.postgresql.org I had to actually raise ulimit -n above 1024 to perform this operation, or else I hit my open file limit. You should also notice a marked improvement in the performance of certain operations. From time to time I recommend running a regular 'git gc' to consolidate packs. Newish versions of git feature automatically triggered gc to do these things, precisely to avoid the kinds of problems you describe. The setting "gc.autopacklimit" to determines how many pack files are allowed. I don't know what the default is. If you are especially impatient, you can clone the repository mentioned previously (you will inherit the repacking I've already done) and port your patches over using "git format-patch" and "git am" or even just adding your old repository as a remote and fetching the branches. You can then set the "origin" remote to git.postgresql.org to continue getting updates from there. fdr
On Wed, Jan 14, 2009 at 5:52 PM, Daniel Farina <drfarina@acm.org> wrote: > On Wed, Jan 14, 2009 at 12:58 AM, Dave Page <dpage@pgadmin.org> wrote: >> This happens on the local machine presumably? I used to suffer that >> problem and resolved it with 'ulimit -n 1024' in my bash profile. > > This is because the number of packs in the git.postgresql.org repo is > enormous, which also slows down clones and many other git operations. > Try running "git gc --aggressive" to fix this on your local copy (this > will take a while -- probably hours -- unless you've done it before). Not much opportunity for that during the initial clone :-) Afterward though, yes, I do run gc occasionally, though I haven't tried --aggressive yet. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
On Wed, Jan 14, 2009 at 11:10 AM, Dave Page <dpage@pgadmin.org> wrote: > Afterward though, yes, I do run gc occasionally, though I haven't > tried --aggressive yet. Oh, okay -- I just thought it was because you put the ulimit change in your .profile that you needed it permanently to keep things rolling. After the first gc (which I think should have repacked everything into one file) the 'ulimit -n' change should be obsolete. '--aggressive' will take minutes to an hour if you have packed all the packs together before so that the 'counting objects' phase doesn't take forever. It should result in substantial repository size reduction, presuming you have delta chains similar to that in the git.postgresql.org repository. My '.git' directory is 110M in total, for reference. fdr