On 10/02/2012 10:10 AM, Jean-Louis Martineau wrote:
Attila,
The attached patch fix amstatus and amdump to report that the tape is
write protected.
I mean amcheck and amdump.
I do not have a tape drive on hand so I can't test it. I appreciate if
someone can test it.
Jean-Louis
On 10/02/2012 08:46 AM, Attila Bogár wrote:
Hi Jean-Louis,
On 02/10/12 13:30, Jean-Louis Martineau wrote:
I'd refine the bug: amanda flushes to the write-protected tape, the
dump is removed from the holding disk (of course it's not on tape),
reports the dump were to Daily-24 and re-expects the same tape.
Amanda flushed nothing to the write-protected tape, it tried but it
failed to write it.
The dump should have been left on holding disk.
It's hard to believe it removed the dump from holding disk? Can you
prove it? Show that a dump was done (log file) and it is not on
holding disk (ls)
Sorry - You are right, it did not dropped the data.
Somewhat confused me, that there was a very small delta between Sep
26 and Sep 27.
I checked the reports thoroughly and it was almost all level 1, so I
understand now.
Your bug definition is the correct one.
What is strange is that it didn't write to Daily-25, there might be
a lot of reason.
Daily-25 wasn't loaded into any of the tape drives.
Daily-23 and Daily-24 was loaded.
-- APPENDIX BEGIN
Date : September 24, 2012
*** A TAPE ERROR OCCURRED: [No acceptable volumes found].
There are 607419M of dumps left in the holding disk.
They will be flushed on the next run.
The next 2 tapes Amanda expects to use are: Daily-23, Daily-24.
