>I presume "Tape Size" means amount of tape used, rather than size of
>the whole tape. ...
Correct.
>I am having 5 out of 23 partitions fail to get to tape and 4 of those 5
>complain about lack of tape (log.20010505.0):
>
> FAIL taper zhongsgi /home/data 0 [out of tape]
> FAIL dumper zhongsgi /home/data 0 ["data write: Broken pipe"]
There should be more messages than just these. For instance, at the
very top:
*** A TAPE ERROR OCCURRED: [[writing file: short write]].
Or in the NOTES: section:
taper: tape 041475/lookout kb 38869024 fm 1 writing file: short write
(these are just examples from my own system).
>It seems like I should be getting nowhere near the end of the tape
>with any of these partitions.
Amanda is an amazingly simple program in many ways. Writing to tape is
one of them. It writes until the OS returns an error code. So you need
to find the message Amanda reported about why it stopped writing to tape,
then figure out why the OS told it that.
The tapetype is irrelevant. That only gives Amanda a hint about how
much tape it will have to work with so it can do the planning steps.
It is not used at all once the actual writing starts.
Assuming you don't have some switches on the drive in the wrong position
(e.g. if it supports multiple densities), or you're not doing something
like writing compressed data to the drive with hardware compression also
turned on, then I'd guess it could be something like the drive needs to
be cleaned, or the tapes need to be retensioned (if that applies to your
hardware), or the drive is kicking in auto-cleaning in the middle of a
session, or there may be some kind of SCSI problem that's reporting an
error under some circumstances, which could be bad termination, too much
termination, not enough termination, bad cable, bad connector seating,
bad controller, etc.
>-ken rich
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
