From: "Frank Ch. Eigler" <fche@redhat.com>
To: David Edelsohn <dje@watson.ibm.com>
Cc: overseers@sources.redhat.com
Subject: Re: gcc.gnu.org CVS meta-data corrupt?
Date: Thu, 08 Apr 2004 13:42:00 -0000 [thread overview]
Message-ID: <20040408095048.GD11002@redhat.com> (raw)
In-Reply-To: <200404080404.i3844aT26350@makai.watson.ibm.com>
Hi -
> [...]
> I suspect that something is broken in the CVS meta-data or the
> filesystem backing that directory. This may be a large cause of the
> slowdown if every single CVS update is timing out on that directory.
The same thing happens to ordinary UNIX file access in the area:
processes simply get stuck in "D" state. The system logs are eerily
quiet on the subject. I suspect the machine needs a reboot and an fsck.
Hmm, while poking around, it just froze. :-(
- FChE
next prev parent reply other threads:[~2004-04-08 13:42 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 4:04 David Edelsohn
2004-04-08 13:20 ` Christopher Faylor
2004-04-08 13:42 ` Frank Ch. Eigler
2004-04-08 14:13 ` David Edelsohn
2004-04-08 14:21 ` Christopher Faylor
2004-04-08 13:42 ` Frank Ch. Eigler [this message]
2004-04-08 13:54 ` system rebooted (was Re: gcc.gnu.org CVS meta-data corrupt?) Christopher Faylor
-- strict thread matches above, loose matches on Subject: below --
2004-04-29 19:40 sourceware load problem again? David Edelsohn
2004-04-29 19:45 ` Christopher Faylor
2004-04-08 4:33 gcc.gnu.org CVS meta-data corrupt? David Edelsohn
2004-04-08 4:50 ` Zack Weinberg
2004-04-08 13:46 ` Christopher Faylor
2004-04-08 19:06 ` law
2004-04-08 19:54 ` Christopher Faylor
2004-04-08 16:12 ` Matthew Galgoci
2004-04-05 18:50 htdig and sources.redhat.com loadavg David Edelsohn
2004-04-05 19:36 ` Hans-Peter Nilsson
2004-04-05 19:46 ` Phil Edwards
2004-04-05 19:56 ` Frank Ch. Eigler
2004-04-05 20:03 ` Phil Edwards
2004-04-05 20:36 ` Hans-Peter Nilsson
2004-04-05 21:15 ` Phil Edwards
2004-04-05 21:23 ` Hans-Peter Nilsson
2004-04-05 21:46 ` Phil Edwards
2004-04-05 22:11 ` Hans-Peter Nilsson
2004-04-05 22:26 ` Phil Edwards
2004-04-05 20:48 ` Benjamin Kosnik
2004-04-05 20:52 ` Ian Lance Taylor
2004-04-05 20:57 ` Zack Weinberg
2004-04-08 21:18 ` Gerald Pfeifer
2004-04-05 21:12 ` Hans-Peter Nilsson
2004-04-05 20:51 ` Christopher Faylor
2004-04-05 21:21 ` Matthew Galgoci
2004-04-05 23:36 ` Zack Weinberg
2004-04-06 0:06 ` Matthew Galgoci
2004-04-06 0:17 ` Matthew Galgoci
2004-04-06 0:29 ` Zack Weinberg
[not found] ` <cgf@alum.bu.edu>
2004-04-05 21:03 ` David Edelsohn
2004-04-05 21:08 ` Ian Lance Taylor
[not found] ` <ian@airs.com>
2004-04-05 21:14 ` David Edelsohn
2004-04-05 22:51 ` Jason Molenda
2004-04-05 23:39 ` GCC snapshot generation (was Re: htdig and sources.redhat.com loadavg) Zack Weinberg
2004-04-06 14:49 ` htdig and sources.redhat.com loadavg David Edelsohn
2004-04-06 16:18 ` Jonathan Larmour
2004-04-06 16:25 ` David Edelsohn
2004-04-06 16:34 ` Ian Lance Taylor
2004-04-06 16:39 ` Phil Edwards
2004-04-07 2:58 ` Christopher Faylor
2004-04-06 16:41 ` Ian Lance Taylor
2004-04-07 2:59 ` Christopher Faylor
2004-04-06 17:40 ` David Edelsohn
2004-04-06 18:00 ` Jonathan Larmour
2004-04-06 19:43 ` Hans-Peter Nilsson
2004-04-06 19:52 ` Ian Lance Taylor
2004-04-06 19:52 ` Frank Ch. Eigler
2004-04-06 23:24 ` Hans-Peter Nilsson
2004-04-08 14:48 ` gcc.gnu.org CVS meta-data corrupt? David Edelsohn
2004-04-08 14:53 ` Frank Ch. Eigler
2004-04-08 15:18 ` Christopher Faylor
2004-05-02 11:32 ` sourceware load problem again? David Edelsohn
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=20040408095048.GD11002@redhat.com \
--to=fche@redhat.com \
--cc=dje@watson.ibm.com \
--cc=overseers@sources.redhat.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).