From: Christopher Faylor <cgf@redhat.com>
To: Ian Lance Taylor <ian@wasabisystems.com>
Cc: overseers@sourceware.org
Subject: Re: /sourceware/www is full
Date: Fri, 19 Mar 2004 14:12:00 -0000 [thread overview]
Message-ID: <20040319020753.GB20715@redhat.com> (raw)
In-Reply-To: <m3oeqta9q3.fsf@gossamer.airs.com>
On Thu, Mar 18, 2004 at 08:47:48PM -0500, Ian Lance Taylor wrote:
>Christopher Faylor <cgf@redhat.com> writes:
>
>> >> /sourceware/www is full. This is breaking bugzilla, and probably
>> >> causing numerous other problems.
>> >>
>> >> I'm going to try to find out what the problem is.
>> >
>> >
>> >Most likely log files. They grow throughout the week,
>> >scrolling/compressing on Saturday.
>> >
>> >Remove some old ones.
>>
>> I'm moving some now.
>
>That fixed the immediate problem. Thanks.
>
>We seem to be skating pretty close to the edge, though. The disk
>partition is 23.9G. Before Chris cleaned out the log files, the log
>directory held 1.7G. So even if we discard all the log files, we only
>have 7% of the disk free. And the mailing list archives keep getting
>bigger, and bigger, and bigger....
I can grow the partition at some point. I'd been planning on doing that
but missed that the partition was so close to being full. I guess we
should plan on some downtime this weekend.
cgf
next prev parent reply other threads:[~2004-03-19 2:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m34qslbqje.fsf@gossamer.airs.com>
[not found] ` <20040318170101.A91608@molenda.com>
2004-03-19 1:31 ` Christopher Faylor
2004-03-19 1:47 ` /sourceware/www is full (/www/gcc/htdocs/onlinedocs?) Christopher Faylor
2004-03-19 2:06 ` Jason Molenda
2004-03-19 2:07 ` Joseph S. Myers
2004-03-19 2:17 ` /sourceware/www is full Ian Lance Taylor
2004-03-19 7:50 ` Joseph S. Myers
2004-03-20 0:49 ` Ian Lance Taylor
2004-03-19 14:12 ` Christopher Faylor [this message]
2004-03-20 1:14 ` Jonathan Larmour
[not found] ` <20040318170150.A91803@molenda.com>
2004-03-20 1:09 ` Jason Molenda
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=20040319020753.GB20715@redhat.com \
--to=cgf@redhat.com \
--cc=ian@wasabisystems.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).