Okay, I just realized that this falls in-line directly with when the NBU AVRD scan "pings" all the drives for AVR status. My guess is that this is then in fact, a spurious message.
Can I prevent it from clogging my messages file? We get two of these (one for each tape drive), every three minutes. And thats after turning down the AVRD poll time - I believe it defaults to a tighter interval.
Thanks!
-- Jeff
On Mon, Aug 27, 2001 at 03:17:13PM -0700, Jeffrey Krueger wrote:
Has anyone else noticed *lots* of these messages?
Mon Aug 27 15:00:53 PDT [fuelcell: Java Thread:warning]: Ndmpd8: IOException: Device I/O error. Device may have no tape Mon Aug 27 15:00:53 PDT [fuelcell: Java Thread:warning]: Ndmpd9: IOException: Device I/O error. Device may have no tape Mon Aug 27 15:03:58 PDT [fuelcell: Java Thread:warning]: Ndmpd10: IOException: Device I/O error. Device may have no tape Mon Aug 27 15:03:58 PDT [fuelcell: Java Thread:warning]: Ndmpd11: IOException: Device I/O error. Device may have no tape Mon Aug 27 15:07:02 PDT [fuelcell: Java Thread:warning]: Ndmpd12: IOException: Device I/O error. Device may have no tape Mon Aug 27 15:07:03 PDT [fuelcell: Java Thread:warning]: Ndmpd13: IOException: Device I/O error. Device may have no tape Mon Aug 27 15:10:07 PDT [fuelcell: Java Thread:warning]: Ndmpd14: IOException: Device I/O error. Device may have no tape Mon Aug 27 15:10:08 PDT [fuelcell: Java Thread:warning]: Ndmpd15: IOException: Device I/O error. Device may have no tape
We've got two DLT7000's hooked up as nrst0a and nrst1a to an F840 - this seems to happen for both drives. 6.1.1 loves telling us this error. We seem to be able to get backups (except for the bug on two of our volumes).
This is occurring on two F840's, two others work fine. Do I just need to fix my tape drives or is anyone else noticing this problem as well?
-- Jeff