From: law@redhat.com
To: Christopher Faylor <cgf@alum.bu.edu>
Cc: Zack Weinberg <zack@codesourcery.com>,
David Edelsohn <dje@watson.ibm.com>,
overseers@sources.redhat.com
Subject: Re: gcc.gnu.org CVS meta-data corrupt?
Date: Thu, 08 Apr 2004 19:06:00 -0000 [thread overview]
Message-ID: <200404081906.i38J6h5k028370@speedy.slc.redhat.com> (raw)
In-Reply-To: Your message of "Thu, 08 Apr 2004 09:46:53 EDT." <20040408134653.GB2967@coc.bosbc.com>
In message <20040408134653.GB2967@coc.bosbc.com>, Christopher Faylor writes:
>I would think that if there were disk problems we'd be seeing something
>in the logs. When I was setting up this system in the beginning I had a
>disk failure after about a month of operation (which didn't fill me with
>wild confidence about Dell quality) but the messages file had error
>messages.
Search for EXT in the logs -- there were certainly errors in the log when I
looked last night.
jeff
next prev parent reply other threads:[~2004-04-08 19:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 4:33 David Edelsohn
2004-04-08 4:50 ` Zack Weinberg
2004-04-08 13:46 ` Christopher Faylor
2004-04-08 19:06 ` law [this message]
2004-04-08 19:54 ` Christopher Faylor
2004-04-08 16:12 ` Matthew Galgoci
-- strict thread matches above, loose matches on Subject: below --
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 13:42 ` Frank Ch. Eigler
2004-04-08 14:13 ` David Edelsohn
2004-04-08 14:21 ` Christopher Faylor
[not found] ` <cgf@alum.bu.edu>
2004-04-08 14:48 ` David Edelsohn
2004-04-08 14:53 ` Frank Ch. Eigler
2004-04-08 15:18 ` Christopher Faylor
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=200404081906.i38J6h5k028370@speedy.slc.redhat.com \
--to=law@redhat.com \
--cc=cgf@alum.bu.edu \
--cc=dje@watson.ibm.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).