On Fri, 1 Dec 2006, Kern Sibbald wrote: > It appears to me that you have run into some sort of race condition where two > threads want to use the same Volume and they were both given access. > Normally that is no problem. However, one thread wanted the particular > Volume in drive 0, but it was loaded into drive 1 so it decided to unload it > from drive 1 and then loaded it into drive 0, while the second thread went on > thinking that the Volume could be used in drive 1 not realizing that in > between time, it was loaded in drive 0.
Someting similar has happened here today, except that one job is now hanging waiting for the tape that's in the other drive. > I'll look at the code to see if there is some way we can avoid this kind of > problem. Probably the best solution is to make the first thread simply start > using the Volume in drive 1 rather than transferring it to drive 0. This would be good. Removing an apparent bias towards using Drive0 would be good too, as it causes uneven wear on 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
