Dave Sherohman wrote:
>
> *** THE DUMPS DID NOT FINISH PROPERLY!
>
> *** A TAPE ERROR OCCURRED: [[writing filemark: Input/output error]].
> *** PERFORMED ALL DUMPS TO HOLDING DISK.
>
...
> FAILURE AND STRANGE DUMP SUMMARY:
...
> cat md1 lev 0 FAILED [out of tape]
> taper: FATAL syncpipe_get: w: unexpected EOF
...
> STATISTICS:
> Total Full Daily
> -------- -------- --------
> Dump Time (hrs:min) 0:12 0:00 0:00 (0:12 start)
> Output Size (meg) 5584.3 569.8 5014.5
> Original Size (meg) 14467.9 2202.4 12265.5
> Avg Compressed Size (%) 38.6 25.9 40.9
> Tape Used (%) 27.3 2.8 24.5 (level:#disks ...)
> Filesystems Dumped 15 7 8 (1:8)
> Avg Dump Rate (k/s) 460.3 1032.8 433.0
> Avg Tp Write Rate (k/s) -- -- --
>
> DUMP SUMMARY:
> DUMPER STATS TAPER STATS
> HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
> -------------------------- -------------------------------------- --------------
> bradley md10 1 FAILED --------------------------------------------
> bradley md6 1 69220 29568 42.7 0:50 592.6 N/A N/A
> ...
>
> ----- End forwarded message -----
You broke the report off just too early :-)
First Amanda said that it was writing md1 from host "cat" to tape
while it ran out of tape.
In the NOTES section of the Amanda report you'll find something
like: (cut from my last archive report)
> NOTES:
> taper: tape ARCHIVE-040 kb 34115424 fm 111 writing file: short write
> driver: going into degraded mode because of tape error.
>From the taper line there, I can see that my backup ran into EOT
while writing 34115424 Kbytes (file 111).
Of course the last dump is not useful, so in the STATISTICS section
it reports only (for my report) 110 files, and it's used space:
> Tape Size (meg) 30922.6 30922.6 0
> Tape Used (%) 81.5 81.5 0 (level:#disks ...)
> Filesystems Taped 110 110 0
So the tape contains 30922 Mbytes USEFUL backup data, and that's
81.5% of the capacity I stated in the tapetype definition:
38000 mbytes / ( 30922 Mbytes + (110 * 500 Kbyte/filemark) )= 0.815 = 81.5 %
The rest of the tape was filled while writing an image that ran into EOT,
but is not calculated in this amount.
>
> So, first off, the big question: Why is amanda first claiming that it
> ran out of tape, then saying that only 27.3% of the tape was used?
It ran out of tape somewhere after 27.3%. For an exact amount of Kilobytes
see the NOTES section in the Amanda report.
You can adjust the capacity you specified in your tapetype definition
if you feel you were a bit optimistic.
Or your capacity is for not-hardware compression, and you use both
hard- and software compression... resulting in LESS native capicity on tape.
Or you ran into an error somewhere halfway the tape (bad tape? drive? computer?)
Look into the system logs to find out (dmesg, syslog, etc).
--
Paul Bijnens, Lant Tel +32 16 40.51.40
Interleuvenlaan 15 H, B-3001 Leuven, BELGIUM Fax +32 16 40.49.61
http://www.lant.com/ email: [EMAIL PROTECTED]
***********************************************************************
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***********************************************************************
