On Tuesday 20 February 2007 09:05, Erik P. Olsen wrote: > Frank Sweetser wrote: > > On Tue, Feb 20, 2007 at 01:04:44AM +0100, Erik P. Olsen wrote: > >> I wasn't aware that it was important to run dbcheck at certain > >> intervals. So I sat it up about 8 hours ago. It showed 4919334 orphaned > >> file records and it is now deleting them. How long time is it supposed > >> to take? It has now been deleting for almost 8 hours and mysqld takes > >> about 85% of the cpu. Is it looping or is it just what I should expect? > > > > It can easily take that long, especially if you're missing some table > > indexes. > > > > http://paramount.ind.wpi.edu/wiki/doku.php?id=faq#why_does_dbcheck_take_f > >orever_to_run > > Well, it is still running now 16 hours after launch. In that case I think > dbcheck ought to have a sort of progress indication, a counter perhaps.
That would be a nice patch for someone to submit. The current development version probably eliminates the need for a counter because it breaks the work up into more reasonable size chunks, so it *should* run much faster. ------------------------------------------------------------------------- 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
