From: "Frank Ch. Eigler" <fche@redhat.com>
To: overseers@sourceware.org
Subject: mystery disk usage growth spurts
Date: Sat, 05 Mar 2016 16:48:00 -0000 [thread overview]
Message-ID: <20160305164130.GF8336@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 631 bytes --]
Hi -
According to PCP archive data [1] [2], over the last few weeks, something
or someone over at sourceware's /sourceware1 partition has consumed
quite some room, in three bursts of some 90GB each:
2016-02-11 12:50-15:00
2016-02-19 13:30-14:20
2016-03-01 18:25-19:25
The irregularity of the schedule makes it unlikely to be a cron job.
Disk utilization curves from the same time make it seem like a
-copies- are being made as opposed to new content.
Does someone have any suspects as to where to start looking?
[1] http://tinyurl.com/h5nzvfw
[2] https://sourceware.org/grafana/index.html#/dashboard/file/default.json
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]
next reply other threads:[~2016-03-05 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 16:48 Frank Ch. Eigler [this message]
2016-03-05 17:16 ` Gerald Pfeifer
2016-03-05 17:41 ` Christopher Faylor
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=20160305164130.GF8336@redhat.com \
--to=fche@redhat.com \
--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).