>> You don't, by any chance, have both hardware and software compression
>> turned on, do you?
>
>How do I tell, exactly? I have a dumptype line reading
>
> compress client fast
>
>But that just seems like which CPU it uses to compute the compression
>algorithm.
This line says you are using software compression. It also happens to
say it's done on the client, but that doesn't really matter.
Since you're using software compression, you **must** turn off hardware
compression. How you do that is highly OS dependent (it's based on the
tape device name for Solaris and AIX, I think it's an "mt" command for
Linux, and so on).
If you want to use hardware compression, you should turn off software
compression with:
compress none
... for all the dumptypes.
I wouldn't advise going that route unless you're having trouble (e.g.
excessive load or wallclock time) with software compression. Software
does a better job (since it can look at longer strings of data) and is
more flexible (you could turn it off for just certain disks whose data
was already compressed, for instance).
>> Which size specification? If you mean the one from taper, it's very
>> accurate (to the KByte).
>
>Good.
By "the one from taper" I was referring to the "taper: tape /dev/whatever
kb NNN fm NNN ..." line in the "NOTES" section of the E-mail (or in the
amdump.NN file). All the other Amanda statistics are based on what was
*successfully* done. So if the image being processed at the time of
the error was large, they could be way off from where the error happened.
>Drew
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
