>  taper: tape DailySet101 kb 1408 fm 1 writing filemark: I/O error
>...
>Now, I know that there is enough room on the tape for what I am backing up.
>(40G tape, /home on the cvs server = 188M, /home on the cclcsup server = 3.1G)

Amanda is just telling you what the OS told it -- there was an I/O error
while trying to write to the tape.  That could be hardware (tape or
drive), the drive may need cleaning, cabling problems or any number of
other things.  But you need to get that fixed before you'll be able to
do reliable backups (with Amanda or anything else).  I'd probably do a
bunch of big "dd bs=32k" I/O tests to the drive (and *scratch* tapes :-).

>  driver: dumper0 pid 2129 is messed up, ignoring it.
>  driver: dumper0 exited with signal 6

This is odd.  It implies the dumper died with an I/O trap (which is
different than the above error -- don't get confused) or it call abort()
on itself.  Are there core files in /tmp/amanda (or wherever)?  Is there
anything else of interest about dumper0 in amdump.<NN>?

>Also, what is the recommended solution for replacing a tape in a tape run?
>i.e. if the tape gets damaged?  Presumably you would need to get a new tape,
>label it the same as the old tape and just add it to the run, right?

Yup.  If the "old" tape has valid data on it, you might run "amrmtape"
to clean out that information.  Or just keep it around until the tapes
cycle and get reused.

>-Josh

John R. Jackson, Technical Software Specialist, jrj AT purdue DOT edu