On Thursday 31 December 2009 09:00:35 JanJaap Scholing wrote: > > > Hi List, > > > All most every night our storage daemon get stuck in a deadlock or > > > something. In every case only a restart of the storage daemon is the > > > only way to get the sd back to work. This is the case: > > > We have 2 pools: > > > Diskpool: contains disk backup volumes.Migratepool: contains the tape > > > autochanger Every night between 17:00 and 6:00 the backups (150+ > > > systems) are made to the diskpool.Every day between 11:00 - until > > > ready, all the backups made to the diskpool are copied to tape using a > > > copy job. At night some of the clients are set to make a backup > > > directly to the migratepool. This are jobs with a large amount of data > > > (200Gb +)In other words, at night backups are made to diskpool and > > > migratepool at the same time. Most of the time the copy jobs (to > > > migratepool) are not ready before he starts with normal backup jobs (to > > > diskpool or migratepool). Normal this is no problem, bacula first makes > > > normal backup jobs, and when ready he goes further with the copy jobs. > > > But in our case this results in a deadlock. > > > Do you have a suggestions to make this better and avoid deadlocks? > > > > This sounds relatively complicated and to answer would require some > > detailed analysis of your configuration, which is "support" and we don't > > do that on this list. > > > > > What can > > > we do? Our bacula server is busy 24x7 make backups and copies. We are > > > using bacula 3.0.3 and debian 5. > > > > Without having a valid backtrace, it is hard to give any specific advice > > on deadlocks. See the kaboom chapter of the manual for info on > > backtraces. If we have a good backtrace and > > Ok, but bacula did not crash. So I don't think i could make a backtrace of > this case.
Bacula does not need to crash to get a backtrace. "See the kaboom chapter of the manual for info on backtraces." > > > I can say that we have corrected three or four deadlock conditions in the > > SD in the current development version. We do not intend to backport > > these changes to the 3.0 branch though. The current development version > > will very likely be released before the end of the month. > > Do you mean the end of Januari 2010? Yes, I jumped ahead a bit too quickly ... > > > If you are having serious problems, you might try getting the current > > development version as it might resolve your problems. At this moment, > > the current git repo seems quite stable, but I caution you, this is a > > development version, and so sometimes we make a small change and it > > breaks a lot of stuff. We still have more work to do before we > > officially release it. One major problem in trying the new version is > > that it requires a database upgrade, and you cannot go back. So I don't > > recommend using it unless you *really* know Bacula extremely well. > > > > Best regards, > > > > Kern > > _________________________________________________________________ > Kakker, Party of Nerd: download ze gratis voor in je Messenger > http://buddytest.rulive.nl/default.aspx?src=taglines ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
