We've been getting strange problems with amanda that we can't figure out...
here's an excerpt from the last backup report:
These dumps were to tape VOL02.
*** 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: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
hannibal /usr2/boston lev 0 FAILED [out of tape]
hannibal /usr2/systems lev 0 FAILED [can't switch to incremental dump]
hannibal /usr2/homes lev 0 FAILED [can't switch to incremental dump]
hannibal /usr2/eng lev 0 FAILED [can't switch to incremental dump]
STATISTICS:
Total Full Daily
-------- -------- --------
Estimate Time (hrs:min) 0:12
Run Time (hrs:min) 0:34
Dump Time (hrs:min) 0:21 0:21 0:00
Output Size (meg) 1963.3 1963.3 0.0
Original Size (meg) 2566.3 2566.3 0.0
Avg Compressed Size (%) 76.5 76.5 --
Filesystems Dumped 7 7 0
Avg Dump Rate (k/s) 1597.1 1597.1 --
Tape Time (hrs:min) 0:02 0:02 0:00
Tape Size (meg) 179.0 179.0 0.0
Tape Used (%) 0.5 0.5 0.0
Filesystems Taped 5 5 0
Avg Tp Write Rate (k/s) 1397.6 1397.6 --
NOTES:
planner: Last full dump of hannibal:/usr2/backup on tape overwritten in 1
run.
planner: Last full dump of hannibal:/usr2/data on tape overwritten in 1
run.
planner: Last full dump of hannibal:/usr2/pub on tape overwritten in 1
run.
planner: Last full dump of hannibal:/usr2/hr on tape overwritten in 1
run.
planner: Adding new disk hannibal:/usr2/eng.
planner: Adding new disk hannibal:/usr2/homes.
planner: Adding new disk hannibal:/usr2/mrtg.
planner: Adding new disk hannibal:/usr2/systems.
taper: tape VOL02 kb 183264 fm 5 writing filemark: Input/output error
driver: going into degraded mode because of tape error.
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-------------------------- --------------------------------- ------------
hannibal -sr2/backup 0 10 32 320.0 0:001071.1 0:03 25.0
hannibal -sr2/boston 0 753070 542528 72.0 5:441578.0 N/A N/A
hannibal -2/business 0 290660 180992 62.3 1:551573.8 2:011501.6
hannibal /usr2/data 0 10 32 320.0 0:00 346.9 0:03 24.0
hannibal /usr2/eng 0 FAILED ---------------------------------------
hannibal /usr2/homes 0 FAILED ---------------------------------------
hannibal /usr2/hr 0 7150 1664 23.3 0:021043.0 0:03 620.9
hannibal /usr2/mrtg 0 15755501284832 81.5 13:181610.7 N/A N/A
hannibal /usr2/pub 0 1420 384 27.0 0:01 658.8 0:03 159.0
hannibal -r2/systems 0 FAILED ---------------------------------------
(brought to you by Amanda version 2.4.2p2)
***************************************************************************
As you can see, for some reason, Amanda doesn't/can't write more than
several GB to the tape, even though we are using 40GB/80GB tapes. I have
compression turned off on the tape itself, and none of these directores are
the holding disk. Anyone have any suggestions? Could this be a problem
with my tapetype? Here's the tapetype definition we've been using:
define tapetype DLT {
comment "DLT tape drives"
length 40000 mbytes # 40 Gig tapes
filemark 2000 kbytes # I don't know what this means
speed 3072 kbytes # 1.5 Mb/s
}
Any suggestions are GREATLY appreciated
Chris Heiser
Communications Systems Engineer
Sentito Networks
