>*** A TAPE ERROR OCCURRED: [[closing tape: Input/output error]]. This comes from a couple of places in Amanda, but the most likely is that Amanda was all done and was just finishing up. The tape is *probably* OK, but I wouldn't bet everything on it.
> taper: FATAL syncpipe_get: w: unexpected EOF I think this is fixed in the current sources. >... is the [out of tape] error true? ... That error means Amanda got an error writing to the last tape you told it it could use (runtapes) so it (Amanda) is out of tape. It does not literally mean the error on this particular tape was that it ran out of space. >I found the following in the server's messages file: > >Feb 8 07:25:48 storage /kernel: (sa0:bt0:0:1:0): CCB 0xcde9e300 - timed out > >Now, this sort of looks like a bad tape. ... Or some other kind of hardware problem. Timeouts are a bad thing. >... I thought amanda was supposed to be able to figure >things so everything fits on a tape. ... It takes all the estimated dump sizes and fits them into the total amount of space you told it it could have on tape (runtapes * the tapetype size). If the real dump is larger than the estimate, or the tape is shorter (including getting an error), then there isn't a lot Amanda can do about that. If you're using compression, that can also "shorten" the available tape space if the dump does not compress as well as expected. You left out one important line from the E-mail. The one in the NOTES section that shows how much data taper wrote before it got into trouble. If that's close to your tape size, then you may have just banged into the end. If it's way short, then it's a hardware or media problem. >--Ruth Anne John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
