On Wed, 19 Jul 2006, Alan Brown wrote: > 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.
Sounds to me like the director is 100% busy writing stuff out to the database - atleast that's what I've seen then I've seen a seemingly hanging directory on our server. A quick peek with "pstack" (a Solaris tool) gives that one thread has the database lock held and many other threads waiting on the same lock (including the "status dir" thread). -- Peter Eriksson <[EMAIL PROTECTED]> Phone: +46 13 28 2786 Computer Systems Manager/BOFH Cell/GSM: +46 705 18 2786 Physics Department, Linköping University Room: Building F, F203 SE-581 83 Linköping, Sweden http://www.ifm.liu.se/~peter ------------------------------------------------------------------------- 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
