From: Ian Lance Taylor <ian@airs.com>
To: "Dave Korn" <dave.korn@artimi.com>
Cc: "'Zack Weinberg'" <zack@codesourcery.com>, <law@redhat.com>,
<overseers@sources.redhat.com>
Subject: Re: src crippled, cvs inaccessible.
Date: Tue, 05 Apr 2005 17:06:00 -0000 [thread overview]
Message-ID: <m3br8tw3v7.fsf@gossamer.airs.com> (raw)
In-Reply-To: <SERRANOLnprfVzjwPu200000065@SERRANO.CAM.ARTIMI.COM>
"Dave Korn" <dave.korn@artimi.com> writes:
> >> The net result is we have a load average of ~20 due to all the
> >> processes sitting in disk wait. If you're using anoncvs, the
> >> connection refused messages are probably due to the high load
> >> average.
> >
> > Lots and lots of disk wait was a symptom of the RAID having degraded
> > due to a disk failure, the last time...
> >
> > zw
>
>
> Oops. Maybe someone had better take a look at the status in whatever
> drive-monitoring utility comes with the RAID array? It's still going on and
> it has been continuing for over six hours now and that is *unusual* and
> therefore scary.....
We did check the RAID.
The current load is not really unusual, unfortunately. There is new
hardware in the queue somewhere at Red Hat, but I don't have any more
information on it.
Ian
next prev parent reply other threads:[~2005-04-05 17:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 15:00 Dave Korn
2005-04-05 15:15 ` Ian Lance Taylor
2005-04-05 15:28 ` Dave Korn
2005-04-05 15:17 ` Jeffrey A Law
2005-04-05 15:20 ` Dave Korn
2005-04-05 16:54 ` Zack Weinberg
2005-04-05 16:59 ` Dave Korn
2005-04-05 17:06 ` Ian Lance Taylor [this message]
2005-04-05 15:23 ` Jonathan Larmour
2005-04-05 15:31 ` Dave Korn
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=m3br8tw3v7.fsf@gossamer.airs.com \
--to=ian@airs.com \
--cc=dave.korn@artimi.com \
--cc=law@redhat.com \
--cc=overseers@sources.redhat.com \
--cc=zack@codesourcery.com \
/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).