From: Chris Faylor <cgf@cygnus.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: overseers@sources.redhat.com
Subject: Re: Imminent disk failure on /dev/sdd3?
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <20000727135302.D16416@cygnus.com> (raw)
In-Reply-To: <Pine.BSF.4.10.10007271311460.12466-100000@dair.pair.com>
On Thu, Jul 27, 2000 at 01:31:37PM -0400, Hans-Peter Nilsson wrote:
>If you look at the indexing log at
>~htdigid/gcc/update-log.2000-07-27-fail, you see this line:
>
>cp: db.wordlist: Input/output error
>
>and the update is aborted (gracefully).
>
>I don't know about you, but to me that's the sign of a disk that needs to
>be replaced.
>
>I think I've ruled out my previous changes from failure causes, and it's
>not a disk full error (BTW, there was "lots" of disk left). I manually
>re-started indexing, which succeeded, despite running in parallell with
>the sourceware update (which was also successful).
>
>It's logical to see a beginning disk error with that copy; it's a 400M
>file; the ht://Dig partition gets plenty of exersise. (And it's not
>really needed; I *think* it could be a "mv" just as well).
This could also be a disk in need of an fsck. I've seen this with linux
occasionally.
cgf
WARNING: multiple messages have this Message-ID
From: Chris Faylor <cgf@cygnus.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: overseers@sources.redhat.com
Subject: Re: Imminent disk failure on /dev/sdd3?
Date: Thu, 27 Jul 2000 10:53:00 -0000 [thread overview]
Message-ID: <20000727135302.D16416@cygnus.com> (raw)
Message-ID: <20000727105300.sI93ppzsf0FDqOddOw9RbDuRSLHoKA2YZmzsJsuY0m4@z> (raw)
In-Reply-To: <Pine.BSF.4.10.10007271311460.12466-100000@dair.pair.com>
On Thu, Jul 27, 2000 at 01:31:37PM -0400, Hans-Peter Nilsson wrote:
>If you look at the indexing log at
>~htdigid/gcc/update-log.2000-07-27-fail, you see this line:
>
>cp: db.wordlist: Input/output error
>
>and the update is aborted (gracefully).
>
>I don't know about you, but to me that's the sign of a disk that needs to
>be replaced.
>
>I think I've ruled out my previous changes from failure causes, and it's
>not a disk full error (BTW, there was "lots" of disk left). I manually
>re-started indexing, which succeeded, despite running in parallell with
>the sourceware update (which was also successful).
>
>It's logical to see a beginning disk error with that copy; it's a 400M
>file; the ht://Dig partition gets plenty of exersise. (And it's not
>really needed; I *think* it could be a "mv" just as well).
This could also be a disk in need of an fsck. I've seen this with linux
occasionally.
cgf
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Hans-Peter Nilsson
2000-07-27 10:31 ` Hans-Peter Nilsson
2000-12-30 6:08 ` Jeffrey A Law
2000-07-28 17:13 ` Jeffrey A Law
2000-12-30 6:08 ` Jim Kingdon
2000-08-05 23:17 ` Jim Kingdon
2000-12-30 6:08 ` Chris Faylor [this message]
2000-07-27 10:53 ` Chris 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=20000727135302.D16416@cygnus.com \
--to=cgf@cygnus.com \
--cc=hp@bitrange.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).