Tape error - how 'bad' is this?
2004-05-11 05:06:56
Hi,
Many months of happy activity and then suddenly, last two nights, the
AMANDA job has failed to finish properly - the error in the AMANDA
report says:
>> These dumps were to tape Daily-014.
>> *** A TAPE ERROR OCCURRED: [[writing file: Input/output error]].
>> Some dumps may have been left in the holding disk.
>> Run amflush to flush them to tape.
>> The next tape Amanda expects to use is: Daily-015.
>>
>> FAILURE AND STRANGE DUMP SUMMARY:
>> halcyon /root lev 0 FAILED [out of tape]
>>
>> [...]
>>
>> STATISTICS:
>> Total Full Daily
>> -------- -------- --------
>> Estimate Time (hrs:min) 0:45
>> Run Time (hrs:min) 8:09
>> Dump Time (hrs:min) 8:15 0:25 7:50
>> Output Size (meg) 10606.2 1315.9 9290.3
>> Original Size (meg) 22351.7 2115.1 20236.6
>> Avg Compressed Size (%) 47.5 62.2 45.9 (level:#disks ...)
>> Filesystems Dumped 54 28 26 (1:21 2:4 4:1)
>> Avg Dump Rate (k/s) 365.7 888.3 337.6
>>
>> Tape Time (hrs:min) 0:14 0:08 0:06
>> Tape Size (meg) 612.8 332.6 280.2
>> Tape Used (%) 1.7 1.0 0.7 (level:#disks ...)
>> Filesystems Taped 36 26 10 (1:10)
>> Avg Tp Write Rate (k/s) 745.4 745.0 745.9
>>
>> [...]
>>
>> taper: tape Daily-014 kb 653792 fm 37 writing file: Input/output error
>> driver: going into degraded mode because of tape error.
I notice it mentions "out of tape" above - that's definitely wrong.
There's certainly plenty of room for all the dumps.
And in the kernel logs for the AMANDA server:
>> [...] kernel: st0: Error with sense data: Info fld=0x8000, Deferred st09:00:
>> sns
>> += f1 4
>> [...] kernel: ASC=15 ASCQ= 1
>> [...] kernel: Raw sense data:0xf1 0x00 0x04 0x00 0x00 0x80 0x00 0x16 0x00
>> 0x00
>> +0x4f 0xc8 0x15 0x01 0x00 0x00 0x00 0x00 0x82 0x01 0x55 0x00 0x00 0x25 0x3b
>> 0x00 0x96 0x32 0x50 0x00
>> [...] kernel: st0: Error with sense data: Info fld=0x1, Current st09:00: sns
>> =
>> +f0 3
>> [...] kernel: ASC=15 ASCQ= 2
>> [...] kernel: Raw sense data:0xf0 0x00 0x03 0x00 0x00 0x00 0x01 0x16 0x00
>> 0x00
>> +0x4f 0xc8 0x15 0x02 0x00 0x00 0x00 0x00 0x82 0x01 0x55 0x00 0x00 0x25 0x3b
>> 0x00 0x96 0x32 0x50 0x00
>> [...] kernel: st0: Error on write filemark.
>> [...] kernel: st0: Error with sense data: Info fld=0x8000, Deferred st09:00:
>> sns
>> += f1 4
>> [...] kernel: ASC=15 ASCQ= 1
>> [...] kernel: Raw sense data:0xf1 0x00 0x04 0x00 0x00 0x80 0x00 0x16 0x00
>> 0x00
>> +0x4f 0xc8 0x15 0x01 0x00 0x00 0x00 0x00 0x82 0x01 0x55 0x00 0x00 0x25 0x3b
>> 0x00 0x96 0x32 0x50 0x00
>> [...] kernel: st0: Error with sense data: Info fld=0x1, Current st09:00: sns
>> =
>> +f0 3
>> [...] kernel: ASC=15 ASCQ= 2
>> [...] kernel: Raw sense data:0xf0 0x00 0x03 0x00 0x00 0x00 0x01 0x16 0x00
>> 0x00
>> +0x4f 0xc8 0x15 0x02 0x00 0x00 0x00 0x00 0x82 0x01 0x55 0x00 0x00 0x25 0x3b
>> 0x00 0x96 0x32 0x50 0x00
>> [...] kernel: st0: Error with sense data: Info fld=0x8000, Deferred st09:00:
>> sns
>> += f1 4
>> [...] kernel: ASC=15 ASCQ= 1
>> [...] kernel: Raw sense data:0xf1 0x00 0x04 0x00 0x00 0x80 0x00 0x16 0x00
>> 0x00
>> +0x4f 0xc8 0x15 0x01 0x00 0x00 0x00 0x00 0x82 0x01 0x55 0x00 0x00 0x25 0x3b
>> 0x00 0x96 0x32 0x50 0x00
>> [...] kernel: st0: Error with sense data: Info fld=0x1, Current st09:00: sns
>> =
>> +f0 3
>> [...] kernel: ASC=15 ASCQ= 2
>> [...] kernel: Raw sense data:0xf0 0x00 0x03 0x00 0x00 0x00 0x01 0x16 0x00
>> 0x00
>> +0x4f 0xc8 0x15 0x02 0x00 0x00 0x00 0x00 0x82 0x01 0x55 0x00 0x00 0x25 0x3b
>> 0x00 0x96 0x32 0x50 0x00
>> [...] kernel: st0: Error on write filemark.
What looks like the problem here? The drive itself? The SCSI
controller? We have a HP DLT-40 drive on an Adaptec 29160 controller.
There have been no configuration changes to the server.
Dave.
--
Dave Ewart
Dave.Ewart AT cancer.org DOT uk
Computing Manager, Epidemiology Unit, Oxford
Cancer Research UK
PGP: CC70 1883 BD92 E665 B840 118B 6E94 2CFD 694D E370
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Tape error - how 'bad' is this?,
Dave Ewart <=
|
|
|