How about trussing mt and looking at the return status of the tape ioctls? You might work out more of what's going on by checking the man pages and/or .h files for the meaning of a return which mt only interprets as a generic error I/O error.
On Wednesday, January 15, 2003, at 02:48 PM, Dave Belfer-Shevett wrote:
We have a pair of Overland AIT-2 tape changers installed on an Ultra-160.
We were using 'rmt' and ufsdump to dump data to individual tapes on the
drive, and using 'mtx' to change tapes as we moved along.
Problem is, we're getting nothing but I/O errors from the drives now.
Here's what happens if I do an 'mt -f /dev/rmt/1 status':
Jan 15 14:29:19 tub.ma.intuit.com scsi: [ID 193665 kern.info] sgen54 at
glm3: target 6 lun 0
Jan 15 14:29:19 tub.ma.intuit.com genunix: [ID 936769 kern.info] sgen54 is
/pci@1f,2000/IntraServer-Ultra160,scsi@1,1/sgen@6,0
Jan 15 14:30:12 tub.ma.intuit.com scsi: [ID 365881 kern.info]
/pci@1f,2000/IntraServer-Ultra160,scsi@1,1/st@4,0 (st25):
Jan 15 14:30:12 tub.ma.intuit.com <Vendor 'SONY ' Product
'SDX-700C '>
Jan 15 14:30:12 tub.ma.intuit.com scsi: [ID 193665 kern.info] st25 at
glm3: target 4 lun 0
--- Send mail for the `bblisa' mailing list to `[EMAIL PROTECTED]'. Mail administrative requests to `[EMAIL PROTECTED]'.
