>Now, I'm using a Mammoth drive in an Exabyte library, with 20GB tapes.
>...From what I've gathered, the
>"no space left on device" indicates a full tape ...
That's probably what it means. You'd have to ask the folks who wrote
the tape driver to be certain.
>yet the statistics show
>that only 33% of the tape was used. ...
That 33% number is the amount of data written to tape compared with the
"use" value from your tapetype. In other words, it depends entirely on
what you put in your tapetype, not on what physically happened.
Also, it only includes the images that successfully made it to tape.
It does not take into account the image that was being written when the
error happened. In other words, it could be almost 6.2 GBytes larger
than the summary numbers indicate.
>... I'm just confused as
>to why it didn't finish. If all of the dumps together were only 12.2 GB
>there should not have been any problem fitting them on a 20GB tape.
Yup. But Amanda is just telling you what the OS told it. To get any
further information about what can trigger this specific error response,
you'll have to talk to the OS tape driver folks.
About the only thing that comes to mind, other than a bad tape or some
other hardware problem, is whether you have both hardware and software
compression enabled. That is known to actually expand data, although
I doubt it would be as extreme as what you're seeing.
Also, the number to pay most attention to in the Amanda report is
the "taper" line in the NOTES section. The 6625.1 tape size number
is the amount successfully written to tape (i.e. the 86 file systems).
The "taper" line will tell you how far along it was, including the image
it was working on when it ran into trouble.
>Eric
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
