> What could be wrong with the "update slots scan" command? My bacula > installation drops InChanger state for tapes on random periodically, but > mostly after I swap one of them. I usually run "update slots=N scan" after > replacing a tape and it works without complaints, e.g. it successfully > updates this particular slot N (even though "slots=N" option was somehow > dropped from the documentation recently). It also usually works for some days > after that, e.g. tapes are properly located by director and "list media" > shows correct InChanger status. Then after a few days InChanger bit for a > random number of tapes gets reset to 0. The cure is to run update with full > scan for all slots, i.e. "update slots scan" but it only helps temporarily. I > have regenerated database three times and checked all MySQL tables and it > does not help. Anyone else noticed this? > Ivan, I have not ever seen this but I it is has been at least 10 months since I have used bacula 1.38. And I believe it was only briefly that I used that version as I got my changer about 1 year ago. I have never used update slots=N scan. I just use update slots. My changer has a barcode reader in it and it automatically scans every tape I put into it so the update slots command usually completes in less than a second.
John BTW, You really need to upgrade to 2.0.3 or 2.2.0 (if possible) as a lot of improvements in handling autochangers have been introduced since 1.38.11. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
