On Wed, 19 Jul 2006, Kern Sibbald wrote: > Can you clarify one point? When you say that when the job is using drive0 the > SD is fine, do you mean that it can use drive1 as well, but when using > drive1, drive 0 cannot be accessed? I would be *very* surprised if the SD > does not handle drives identically. Anything is possible, but I don't see how > the code could do that.
Not only Drive0, but also a "status director" leads to indefinite hang too. This seems to clear when the file being flushed to tape finally finishes, but of course when running concurrent jobs there's always another file ready to flush - if that is to drive0 then things are normal again (and drive1 flushes happily too), but if it is to drive1 then the wedge situation recurs. Selection of drive0/1 for spool files ready to flush seems to be a race condition. Possibly related, when jobs are run, if one ends up waiting on the changer for an appropriate tape, all the jobs behind it are also held up, even if some of them can use the tapes in the drives. AB ------------------------------------------------------------------------- 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
