Hi,
Does anyone now why Amanda might generate an out of tape error in a
situation where it blatantly isn't anywhere even close to the end of the
tape?
I'm dumping four servers to an external Ultrium 100/200Gb unit, with
hardware compression turned off, and the largest filesystem failed last
night. Selected excerpts from the log:-
======================================================================
*** A TAPE ERROR OCCURRED: [[writing filemark: 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: ACU-STD-15.
FAILURE AND STRANGE DUMP SUMMARY:
castor sda12 lev 1 STRANGE
castor sda8 lev 0 STRANGE
castor sda10 lev 0 FAILED [out of tape]
======================================================================
the filesystem in question:-
======================================================================
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
----------------- --------------------------------------- -------------
castor sda10 0 36167772 20726828 57.3 188:08 1836.2 FAILED ------
======================================================================
and the notes:-
======================================================================
NOTES:
planner: Incremental of pollux:sda8 bumped to level 2.
planner: Incremental of castor:sda8 bumped to level 2.
planner: Incremental of yildun:hda6 bumped to level 2.
taper: tape ACU-STD-14 kb 9456384 fm 29 writing filemark: Input/output
error
driver: going into degraded mode because of tape error.
======================================================================
The tapetype entry was generated for this drive by running amtapetype,
and is:-
define tapetype HP-ULTRIUM-230 {
comment "HP Ultrium 230e"
length 101376 mbytes
filemark 0 kbytes
speed 13855 kps
}
I've had successful runs with more data than this one would have had -
is this just a glitch, or is there something I can/should be doing about it?
Mike.
