Imminent disk failure on /dev/sdd3?

Imminent disk failure on /dev/sdd3?

[Hans-Peter Nilsson]

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).

brgds, H-P

Re: Imminent disk failure on /dev/sdd3?

[Chris Faylor]

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

Re: Imminent disk failure on /dev/sdd3?

[Jeffrey A Law]

  In message < Pine.BSF.4.10.10007271311460.12466-100000@dair.pair.com >you write
:
  > 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).
Just so you know, I'm going to have one of the sysadmin types in California
look at it (none of the regular sourceware admins are physically in 
California).

jeff

Re: Imminent disk failure on /dev/sdd3?

[Jim Kingdon]

> Just so you know, I'm going to have one of the sysadmin types in California
> look at it (none of the regular sourceware admins are physically in 
> California).

I might be willing to do such tasks if needed (I work minutes from the
Red Hat Sunnyvale office which is where sources.redhat is located last
I checked).  But if you can get Red Hat IS to do it, that strikes me
as a much better solution from a lot of points of view.

Hmm, I wonder if I should get VA to donate a server with a Mylex RAID
controller and enough disks to make dealing with bad disks easy.  Not
sure VA would give it even if Red Hat wanted to accept it; I'm sort of
thinking out loud.

Re: Imminent disk failure on /dev/sdd3?

[Jim Kingdon]

> Just so you know, I'm going to have one of the sysadmin types in California
> look at it (none of the regular sourceware admins are physically in 
> California).

I might be willing to do such tasks if needed (I work minutes from the
Red Hat Sunnyvale office which is where sources.redhat is located last
I checked).  But if you can get Red Hat IS to do it, that strikes me
as a much better solution from a lot of points of view.

Hmm, I wonder if I should get VA to donate a server with a Mylex RAID
controller and enough disks to make dealing with bad disks easy.  Not
sure VA would give it even if Red Hat wanted to accept it; I'm sort of
thinking out loud.

Re: Imminent disk failure on /dev/sdd3?

[Chris Faylor]

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

Re: Imminent disk failure on /dev/sdd3?

[Jeffrey A Law]

  In message < Pine.BSF.4.10.10007271311460.12466-100000@dair.pair.com >you write
:
  > 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).
Just so you know, I'm going to have one of the sysadmin types in California
look at it (none of the regular sourceware admins are physically in 
California).

jeff

Imminent disk failure on /dev/sdd3?

[Hans-Peter Nilsson]

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).

brgds, H-P