On Tue, Mar 06, 2007 at 03:36:39AM +0000, Alan Brown wrote: > On Mon, 5 Mar 2007, Kern Sibbald wrote: > > >>I'm also seeing this using Bacula 2.0.1 on RHEL-4 with a jukebox > >>holding two LTO-3 drives. It's an intermittent problem that I haven't > >>been able to reproduce reliably, so I haven't opened a bug report on > >>it yet. > > >The above is a known bug (at least to some of us) in 1.38.x. It is fixed > >in 2.0.x > > In my case it's still happening in 2.0.2, the clients don't go away > or die and it seems to be most common when a bunch of jobs kick off > simultaneously.
Yes, I'd noticed that as well. For a while I was running 6 jobs at once, and would get tapes with an error status due to a file count mismatch every day or two. Cutting back to two concurrent jobs greatly reduced the frequency of these errors, but didn't eliminate them. > The interesting this is that the tape is marked in error by the fatal > error, but is then unmarked by another completing job, so when it comes > time to follow up on the error, the number of files on the tape match the > number of files in the catalog. That also sounds familiar. It looks like were both seeing the same error. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
