Shawn ... some thoughts ... look at your device configuration ... where does nst0 point to, the device/channel configuration and the error message don't seem to coincide ... at least on a cursory look -- A vs 0 ... are you sure you're specifying the correct device for the channel that it's on?? Or failing that, after reviewing some of the kernel, there does appear to be some significant changes in the aix7xxx driver family in the past few (and recent) develpment kernels ...
it does appear to be some question on the ability to recognize the driver and or issue it buffers and SCB's ...
My $0.02 worth ... :-)
Dan.
swallbri@mail.synack-hosting.com wrote:
pinky:/# tar -b 1024 -cvf /dev/nst0 /Rogue/Renders/CorePost/CO-202/ > tape0001_CO-202.log tar: Removing leading `/' from member names tar: /dev/nst0: Wrote only 65536 of 524288 bytes tar: Error is not recoverable: exiting now
what is the device specifics for /dev/nst0 (ie: major/minor)
SCSI subsystem driver Revision: 1.00 scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.4 <Adaptec 29160 Ultra160 SCSI adapter> aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
Vendor: SONY Model: SDX-700C Rev: 0101 Type: Sequential-Access ANSI SCSI revision: 02 (scsi0:A:2): 80.000MB/s transfers (40.000MHz, offset 127, 16bit)
st: Version 20020205, bufsize 32768, wrt 30720, max init. bufs 4, s/g segs 16 Attached scsi tape st0 at scsi0, channel 0, id 2, lun 0
Nasty SCSI Error: Dec 10 15:00:55 pinky kernel: scsi0:0:6:0: Attempting to queue an ABORT message ... Dec 10 15:00:55 pinky kernel: DevQ(0:6:0): 0 waiting Dec 10 15:00:55 pinky kernel: scsi0:0:6:0: Device is active, asserting ATN Dec 10 15:00:55 pinky kernel: Recovery code sleeping Dec 10 15:01:00 pinky kernel: Recovery code awake Dec 10 15:01:00 pinky kernel: Timer Expired Dec 10 15:01:00 pinky kernel: aic7xxx_abort returns 0x2003