Hi Jon,
thanks for your answer. i investigated a bit further...
Jon LaBadie schrieb:
taper: tape volume008 kb 310112256 fm 40 writing file: No space left
on device
> ...
ok, that's clear
taper: retrying lore:/local/home/moshkow.0 on new tape: [writing
file: No space left on device]
This is taper again.
I tried that same DLE that failed on the last tape (retrying lore:/local...).
With so little info from the OS I can't really tell what happened, so I'll
print the same guess again. But actually I don't really know if I got to a
different amanda tape or not, I can't even tell you the name of the tape.
So you will have to investigate to determine what is happening.
so maybe this isn't a error message but just a hint...
Jon here again...
Anyway that is what I interpret taper's messages as saying. And if I were
investigating those are the only ones you showed us that I would care about.
Now the questions are things like "is your tape bigger than 310GB" so it should
not have run out?
no, it's 200GB uncompressed, so 310GB is a reasonable value for running
out of tape
Should amanda have been able to find another tape, if yes,
why didn't it? If no, why did it try?
yes, it should have tried and it did suceed:
USAGE BY TAPE:
Label Time Size % Nb
volume008 8:24 296941.8 149.2 39
volume009 2:41 37701.0 18.9 4
so it switched to tape 9 and even wrote some data.
These were the last log entries (concerning taper):
----------------------snip------------------------------
...
INFO taper tape volume008 kb 310112256 fm 40 writing file: No space left
on device
START taper datestamp 20041217 label volume009 tape 1
INFO taper retrying lore:/local/home/moshkow.0 on new tape: [writing
file: No space left on device]
SUCCESS taper lore /local/home/moshkow 20041217 0 [sec 734.254 kb
10928314 kps 14883.5 {wr: writers 42690 rdwait 354.083 wrwait 374.041 fi
lemark 3.803}]
SUCCESS taper kira /home/konvert/zeitschriften/fm 20041217 0 [sec
314.885 kb 2471703 kps 7849.5 {wr: writers 9657 rdwait 247.092 wrwait 65
.786 filemark 1.521}]
...
SUCCESS taper lore /local/home/sokirko/M5 20041217 0 [sec 3004.481 kb
22426366 kps 7464.3 {wr: writers 87604 rdwait 2136.876 wrwait 860.38
0 filemark 1.623}]
...
SUCCESS taper kira /home/konvert/Rest 20041217 0 [sec 5625.615 kb
2779429 kps 494.1 {wr: writers 10859 rdwait 5414.565 wrwait 208.603 file
mark 1.524}]
...
FATAL taper syncpipe_put: Broken pipe
WARNING driver going into degraded mode because of tape error.
----------------------------snap----------------------------------------
Could this "Broken pipe" have come from me killing the taper process
after it got stuck? What a pity there's no timestamp...
Next time i will look into the log *before* i kill some process.
thanks a lot for your hints Jon,
Kai
| 