Arno Lehmann wrote:
Hi all,
as I've seen some error reports with the message given in the subject
line and I'm having some trouble with this myself I think it's useful to
collect some more specific data concerning this special error.
There are some current threads discussing this problem, and
unfortunately, I can't follow them all any more :-(
So, I suggest collecting the relevant information (once more) here.
For me, things look like this:
Bacula DIR version 1.37.38, SD the same, FDs of different beta versions.
The error occured when a job wanted to write to a device which was busy
using a tape from a different pool than the one the failing job requested.
I could not reproduce the problem until now - I started some jobs going
to one device but using different pools, and they correctly waited and
got executed without problems afterwards.
In one case, though, the catalog was not updated correctly: For the
volume in question, the data was written, but in the catalog the number
of files on tape was not set.
I think that - in my case - I can safely say that all this stuff only
happens when jobs are "on hold", waiting for a the device to finish
writing on a tape from a different pool.
Now that you mention it, I do believe this is the case for me also. I
sent the information that Kern requested yesterday (status storage) to
the bacula-devel list but it seems that email never made it there. I'll
send that off again.
Has anybody observed the same, or has cases where the error occured when
no jobs were running on the required storage device?
Arno
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
