Of course, once I mailed the list thanks and said I was up and running, I
started having problems. They listen to us, I tell you.
Anyway, on each of the last three nights, I've had tape errors. This is
what amanda says in her mail:
These dumps were to tape DailySet1-09.
*** 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: a new tape.
And, in /var/log/messages (this is RedHat 6.2), I get:
Nov 3 03:02:44 chaos kernel: st0: Error with sense data: Info fld=0x400,
Deferred st09:00: sense key Medium Error
Nov 3 03:02:44 chaos kernel: Additional sense indicates Write append
position error
Nov 3 03:02:44 chaos kernel: st0: Error with sense data: [valid=0] Info
fld=0x0, Current st09:00: sense key Medium Error
Nov 3 03:02:44 chaos kernel: Additional sense indicates Write append
position error
Nov 3 03:02:44 chaos kernel: st0: Error on write filemark.
Curiously, each of the three times, the tape error occurs just under
3 minutes into the amdump run. Of course, the amflush the next day works
just fine, taking almost an hour to do so. All of these runs (both the
dumps and the flushes) are to brand new tapes.
I'm running 2.4.2 pulled out of CVS on 10/19/00, and my tape drive is an
EXB8505XL in a Sun enclosure hanging off an AHA2940UW. I'm using Exabyte
160m XL tapes.
Any ideas? Thanks.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
