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
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
Hi,
I get similar error messages and have logged a call with Netapp - no reply yet. There is a bug report that appears on now that explains what might be the cause.
Bug ID 33086 Title NDMP IO exceptions due to unexpected socket closure Product Data ONTAP Description The following Data ONTAP error messages are generated when a NDMP TCP/IP socket is unexpectedly closed: June 6 12:37:46 [Ndmpd1]: Top level IOException June 6 12:37:46 [Ndmpd1]: IO exception: Socket closed. These messages are typically caused by NDMP backup applications that terminate TCP/IP socket connections without first closing the associated NDMP session. In this case the NDMP backup or recovery operation completes before the application closes the socket and no failure is evident, even though the IO exception error messages are generated. However these messages can also indicate a network problem resulting in loss of connectivity between the NDMP backup application and the filer or between filers in a 3-way NDMP configuration. In this case any in-progress backup or recovery operations may fail. Examination of the backup application status and/or Data ONTAP NDMP logs will indicate whether a backup or recovery failure occurred. Workaround
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com]On Behalf Of Jeffrey Krueger Sent: Tuesday, August 28, 2001 12:17 AM To: toasters@mathworks.com Subject: Spurious tape drive errors in 6.1+?
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
I have been on the phone with Veritas support for weeks trying to get the ndmp running. I get an error message every time I try to run a tape inventory: process killed by signal (211) and a core file is generated.
Has anyone seen this problem before?