Re: Imminent disk failure on /dev/sdd3?

[Jeffrey A Law <law@cygnus.com>]

  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