git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bryan Turner <bturner@atlassian.com>
To: Andreas Krey <a.krey@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
	Git Users <git@vger.kernel.org>
Subject: Re: Big repo not shrinking on repack or gc?
Date: Thu, 15 Jan 2015 19:56:12 +1100	[thread overview]
Message-ID: <CAGyf7-Hi2YZQZ610uH6iAsQYRNdLndPCy+ArzZpi4Up7NhkpqQ@mail.gmail.com> (raw)
In-Reply-To: <20150115074334.GJ13247@inner.h.apk.li>

On Thu, Jan 15, 2015 at 6:43 PM, Andreas Krey <a.krey@gmx.de> wrote:
> On Thu, 15 Jan 2015 18:05:46 +0000, Bryan Turner wrote:
> ...
>
> They do. So it seems it was forked once upon a time, but...
>
> /opt/apps/atlassian/stash-data/shared/data/repositories $ grep '' */objects/info/alternates
> 158/objects/info/alternates:/data/opt_apps/atlassian/stash-data/shared/data/repositories/20/objects
> 45/objects/info/alternates:/data/opt_apps/atlassian/stash-data/shared/data/repositories/33/objects
> 93/objects/info/alternates:/data/opt_apps/atlassian/stash-data/shared/data/repositories/91/objects
>
> ...there is no trace of a fork still existing (the repo in question is 143).

Yes, the system doesn't currently detect when a repository becomes
un-forked because it's not a common use case.

At this point I think we should probably take this off-list. You can
either e-mail me directly (bturner at atlassian dot com), or, better
still, raise a ticket on support.atlassian.com. Either way I'll work
with you directly to un-fork the repository on disk and allow it to
clean itself up.

>
> Andreas
>
> --
> "Totally trivial. Famous last words."
> From: Linus Torvalds <torvalds@*.org>
> Date: Fri, 22 Jan 2010 07:29:21 -0800

      reply	other threads:[~2015-01-15  8:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14 11:51 Big repo not shrinking on repack or gc? Andreas Krey
2015-01-14 12:49 ` Jeff King
2015-01-14 13:07   ` Andreas Krey
2015-01-14 14:39   ` Andreas Krey
2015-01-14 16:00     ` Andreas Krey
2015-01-14 17:24     ` Junio C Hamano
2015-01-15  1:23       ` Bryan Turner
2015-01-15  6:38         ` Andreas Krey
2015-01-15  7:05           ` Bryan Turner
2015-01-15  7:43             ` Andreas Krey
2015-01-15  8:56               ` Bryan Turner [this message]

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=CAGyf7-Hi2YZQZ610uH6iAsQYRNdLndPCy+ArzZpi4Up7NhkpqQ@mail.gmail.com \
    --to=bturner@atlassian.com \
    --cc=a.krey@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /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).