From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hans-Peter Nilsson To: overseers@sources.redhat.com Subject: Imminent disk failure on /dev/sdd3? Date: Sat, 30 Dec 2000 06:08:00 -0000 Message-id: X-SW-Source: 2000/msg00863.html 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hans-Peter Nilsson To: overseers@sources.redhat.com Subject: Imminent disk failure on /dev/sdd3? Date: Thu, 27 Jul 2000 10:31:00 -0000 Message-ID: X-SW-Source: 2000-q3/msg00154.html Message-ID: <20000727103100.ft7CyZnr1_xaM8mOsdeo_OphPL730jtdc28WathpnXs@z> 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