git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Steven Tweed <d.s.tweed@reading.ac.uk>
To: git@vger.kernel.org
Cc: nico@cam.org, Johannes.Schindelin@gmx.de
Subject: [PATCH] Make git prune remove temporary packs that look like write failures
Date: Tue, 5 Feb 2008 18:49:31 +0000 (GMT)	[thread overview]
Message-ID: <Pine.GSO.4.63.0802051844220.15867@suma3> (raw)

Write errors when repacking (eg, due to out-of-space conditions)
can leave temporary packs (and possibly other files beginning
with "tmp_") lying around which no existing
codepath removes and which aren't obvious to the casual user.
These can also be multi-megabyte files wasting noticeable space.
Unfortunately there's no way to definitely tell in builtin-prune
that a tmp_ file is not being used by a concurrent process.
However, it is documented that pruning should only be done
on a quiet repository. The names of removed files are printed.

Signed-off-by: David Tweed (david.tweed@gmail.com)
---

Per discussion of previous version, this now unconditionally
removes any tmp_ file existing when prune is run.

  builtin-prune.c |   25 +++++++++++++++++++++++++
  1 files changed, 25 insertions(+), 0 deletions(-)

diff --git a/builtin-prune.c b/builtin-prune.c
index b5e7684..9db3cf0 100644
--- a/builtin-prune.c
+++ b/builtin-prune.c
@@ -83,6 +83,30 @@ static void prune_object_dir(const char *path)
  	}
  }

+/*
+ * Write errors (particularly out of space) can result in
+ * failed temporary packs (and more rarely indexes and other
+ * files begining with "tmp_") accumulating in the
+ * object directory.
+ */
+static void remove_temporary_files(void)
+{
+	DIR *dir;
+	struct dirent *de;
+	char* dirname=get_object_directory();
+
+	dir = opendir(dirname);
+	while ((de = readdir(dir)) != NULL) {
+		if (strncmp(de->d_name, "tmp_", 4) == 0) {
+			char name[4096];
+			sprintf(name, "%s/%s", dirname, de->d_name);
+			printf("Removing abandoned pack %s\n", name);
+			unlink(name);
+		}
+	}
+	closedir(dir);
+}
+
  int cmd_prune(int argc, const char **argv, const char *prefix)
  {
  	int i;
@@ -115,5 +139,6 @@ int cmd_prune(int argc, const char **argv, const char *prefix)

  	sync();
  	prune_packed_objects(show_only);
+	remove_temporary_files();
  	return 0;
  }
-- 
1.5.4.19.g40d1a-dirty

             reply	other threads:[~2008-02-05 19:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 18:49 David Steven Tweed [this message]
2008-02-05 19:02 ` [PATCH] Make git prune remove temporary packs that look like write failures Nicolas Pitre
2008-02-05 20:06   ` [PATCH] prune: heed --expire for stale packs, add a test Johannes Schindelin
2008-02-05 20:13     ` Nicolas Pitre
2008-02-06  5:15       ` Junio C Hamano
2008-02-06  7:41         ` Johannes Schindelin
2008-02-06 14:12         ` Nicolas Pitre
2008-02-06 20:30           ` Junio C Hamano
2008-02-06 16:48   ` [PATCH] Make git prune remove temporary packs that look like write failures Brandon Casey
2008-02-06 18:59     ` David Tweed
2008-02-06 19:41       ` Brandon Casey
2008-02-06 19:57         ` David Tweed
2008-02-06 20:07           ` Nicolas Pitre
2008-02-06 20:43           ` Brandon Casey
2008-02-06 19:10   ` David Tweed
2008-02-06 19:31     ` Nicolas Pitre
2008-02-06 20:02       ` David Tweed
2008-02-06 20:16         ` Nicolas Pitre
2008-02-06 20:25           ` David Tweed
2008-02-06 10:02 ` Junio C Hamano

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=Pine.GSO.4.63.0802051844220.15867@suma3 \
    --to=d.s.tweed@reading.ac.uk \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=nico@cam.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).