FYI: Kern added a patch that fixes the problem. It is attached to the bug report at http://bugs.bacula.org/view.php?id=1524
Daniel. * Daniel De Marco <[email protected]> [03/05/2010 16:13]: > I just updated to 5.0.1 and I can confirm the problem is still present. > > I also filed the report at: > http://bugs.bacula.org/view.php?id=1524 > > Daniel. > > * Thomas <[email protected]> [03/05/2010 13:13]: > > Hi Daniel, > > > > > > i see the same behaviour on my systems, > > this problem exists since the "accurate backup" feature was implemented in > > 3.0.0. > > (i don't know if this causes the problem, but it is my favourite candidate > > for that :) ) > > > > someone should file a bug report :) > > > > Thomas > > > > > > > > Daniel De Marco schrieb: > > > Hi, > > > > > > I've been using InitCatalog and Verify jobs to monitor my production > > > machines. This seems to work very well when there are modified files. > > > However if a new files appears in one of the monitored directories then > > > all the files from then on will be reported at the same time as missing > > > and as new files with the same name/path/attributes... > > > > > > I debugged this problem a bit and it seems to be due to the fact that > > > when bacula queries the DB for the file attributes one of the where > > > clauses is the FileIndex. If there are added or missing files the > > > FileIndex is no longer correct for all subsequent files and they are all > > > reported as missing and new. I think a possible solution would be to > > > tweak the local FileIndex variable when doing the Verify pass: so if a > > > file is new don't increment the FileIndex and if a file is missing > > > increment it anyway. In this way the proper FileIndex would be used in > > > the query and only "real" problematic files would be reported. > > > > > > Daniel. > > > > > > ------------------------------------------------------------------------------ > > > Download Intel® Parallel Studio Eval > > > Try the new software tools for yourself. Speed compiling, find bugs > > > proactively, and fine-tune applications for parallel performance. > > > See why Intel Parallel Studio got high marks during beta. > > > http://p.sf.net/sfu/intel-sw-dev > > > _______________________________________________ > > > Bacula-users mailing list > > > [email protected] > > > https://lists.sourceforge.net/lists/listinfo/bacula-users > > > > -- > > [:O]###[O:] > > > > ------------------------------------------------------------------------------ > > Download Intel® Parallel Studio Eval > > Try the new software tools for yourself. Speed compiling, find bugs > > proactively, and fine-tune applications for parallel performance. > > See why Intel Parallel Studio got high marks during beta. > > http://p.sf.net/sfu/intel-sw-dev > > _______________________________________________ > > Bacula-users mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/bacula-users > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Bacula-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/bacula-users ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
