Kern Sibbald wrote:
> Hello,
>
> I regret to have to announce that there is a rather serious bug in Bacula.
Well, at least you've got a fix for it =)
> 8. The data is correctly stored on the Volume, but incorrect index (JobMedia)
> records are stored in the database. (the JobMedia record generated during
> the Volume change contains the index of the new Volume rather than the
> previous Volume).
This implies to me that a purge and bscan should result in a fixed catalog;
correct?
> I have uploaded patches to bug #935 (bugs.bacula.org) that will correct
> version 2.2.0, 2.2.1, and 2.2.2. The patch has been tested only on version
> 2.2.2 and passes all regression tests as well as the specific test that
> reproduced the problem.
Is this patch and/or a regression test that reproduces the bug available in
SVN head? If so, I'll run it through my test systems and let you know how it
goes.
--
Frank Sweetser fs at wpi.edu | For every problem, there is a solution that
WPI Senior Network Engineer | is simple, elegant, and wrong. - HL Mencken
GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel
