git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: git@vger.kernel.org
Subject: git gc leaved my disk 100% full
Date: Tue, 19 Jan 2016 17:09:57 +0100	[thread overview]
Message-ID: <20160119170957.6e69ebb8@endymion.delvare> (raw)

Hi git developers,

Earlier today my desktop environment warned me that my /home was almost
full. I thought that running "git gc" on my git trees would maybe save
some disk space.

Unfortunately the opposite happened. "git gc" failed on me with:

fatal: sha1 file '.git/objects/pack/tmp_idx_XW7opV' write error: No space left on device
error: failed to run repack

and at that point the partition was 100% full. My git repository went
from 2.2 GB to 3.3 GB in the process, this is why.

While I understand the value of preserving temporary files for
debugging purpose, I don't think it makes sense in the context of the
"gc" command which precisely should get rid of such temporary files.

So please consider fixing "gc" so that it cleans up any temporary file
in case of failure.

Thanks,
-- 
Jean Delvare
SUSE L3 Support

             reply	other threads:[~2016-01-19 16:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19 16:09 Jean Delvare [this message]
2016-02-04  7:58 ` git gc leaved my disk 100% full 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160119170957.6e69ebb8@endymion.delvare \
    --to=jdelvare@suse.de \
    --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.
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).