From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: git@vger.kernel.org
Subject: Repacking a repository uses up all available disk space
Date: Sun, 12 Jun 2016 17:25:14 -0400 [thread overview]
Message-ID: <20160612212514.GA4584@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
Hello:
I have a problematic repository that:
- Takes up 9GB on disk
- Passes 'git fsck --full' with no errors
- When cloned with --mirror, takes up 38M on the target system
- When attempting to repack, creates millions of files and eventually
eats up all available disk space
Repacking the result of 'git clone --mirror' shows no problem, so it's
got to be something really weird with that particular instance of the
repository.
If anyone is interested in poking at this particular problem to figure
out what causes the repack process to eat up all available disk space,
you can find the tarball of the problematic repository here:
http://mricon.com/misc/src.git.tar.xz (warning: 6.6GB)
You can clone the non-problematic version of this repository from
git://codeaurora.org/quic/chrome4sdp/breakpad/breakpad/src.git
Best,
--
Konstantin Ryabitsev
Linux Foundation Collab Projects
Montréal, Québec
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2016-06-12 21:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 21:25 Konstantin Ryabitsev [this message]
2016-06-12 21:38 ` Repacking a repository uses up all available disk space Jeff King
2016-06-12 21:54 ` Konstantin Ryabitsev
2016-06-12 22:13 ` Jeff King
2016-06-13 0:24 ` Duy Nguyen
2016-06-13 4:58 ` Jeff King
2016-06-13 1:43 ` Nasser Grainawi
2016-06-13 4:33 ` [PATCH 0/3] repack --keep-unreachable Jeff King
2016-06-13 4:33 ` [PATCH 1/3] repack: document --unpack-unreachable option Jeff King
2016-06-13 4:36 ` [PATCH 2/3] repack: add --keep-unreachable option Jeff King
2016-06-13 4:38 ` [PATCH 3/3] repack: extend --keep-unreachable to loose objects Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160612212514.GA4584@gmail.com \
--to=konstantin@linuxfoundation.org \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).