From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: overseers@sourceware.org
Subject: Re: mystery disk usage growth spurts
Date: Sat, 05 Mar 2016 17:41:00 -0000 [thread overview]
Message-ID: <20160305174107.GA786@ednor.casa.cgf.cx> (raw)
In-Reply-To: <alpine.LSU.2.20.1603050955350.3951@anthias>
On Sat, Mar 05, 2016 at 10:16:33AM -0700, Gerald Pfeifer wrote:
>On Sat, 5 Mar 2016, Frank Ch. Eigler wrote:
>> Does someone have any suspects as to where to start looking?
>
>I checked ~ftp/pub/gcc, and that only had 30G in total (which I
>brought down to 22G by removing older snapshots).
>
>/www/gcc/ is at 53G, which first surprised me, but includes all
>mailing list archives and online documentation, and clearly is
>not the source of what you are looking for.
>
>Nothing crazily large under /home or /log, either.
How about ~cygwin ?
% du -s ~cygwin | comma
243,951,236 /sourceware/cygwin-staging
cgf
next prev parent reply other threads:[~2016-03-05 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 16:48 Frank Ch. Eigler
2016-03-05 17:16 ` Gerald Pfeifer
2016-03-05 17:41 ` Christopher Faylor [this message]
2016-03-05 22:02 ` Frank Ch. Eigler
2016-03-06 15:37 ` Jon Turney
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=20160305174107.GA786@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).