I send this to -users and -devel because I don't know if the original poster is on -devel where this belongs, IMO...
On 2/25/2007 3:43 AM, Dan Langille wrote: > On 25 Feb 2007 at 3:33, Florian Heigl wrote: > > >>Just a silent heads up, if I may... > > > Umm, how is this silent? ;) Probably because Florian wrote that without mumbling the words while typing? ;-) > >>I never noticed bacula didn't track media errors, but this *is* a missing >>feature Yes, and that's part of the reason for the feature request Adam and I submitted some time ago :-) I wasn't aware of the difference between soft and hard errors, but that's obviously important. >> - the backup tool is expected to have error counters for tape devices >>and media, both will fail lots once things scale up as they're just parts that >>wear off over time and one needs an indicator for replacing things on time. >> >>usually a tape should be blocked from being recycled after a certain point >>and a tape drive should be disabled for intervention. > > > Sounds like you want to get this onto the projects page,and ready for > the next vote. In my opinion that has already taken place: Item 25: Improve Bacula's tape and drive usage and cleaning management. Currently item 7 - and I notice that the projects page on the web site is kind of broken. The overview and the actual descriptions are not representing the current state, I believe. > Or someone could just do the work. If this is to be done, it must be > modular: not every OS will collect the errors the same way. It may > even differ from device to device. I had discussed some of that with Kern quite a while ago. He suggested to keep the 'status poller' in an extra script or program, similar to mtx-changer. That does sound reasonable, and there even is a configuration directive for that purpose in existence: AlertCommand. We would only need a defined interface to return status information in a way that the SD can easily parse. In the thread 'Cleaning Jobs' on -users I presented some ideas that could be used, because the problem of cleaning job and this one here are tightly related: Basically, and as a first step, it's about getting status information from the drive at regular intervals. These need to be passed to the DIR, which could put them into the catalog, and which would have to determine if any action is necessary - drive cleaning, requesting operator assistence, or disabling the drive or tape altogether. Looks like Adam and I did not understand what our feature request should have contained, but we can always rewrite it. Quite soon, possibly :-) Arno -- IT-Service Lehmann [EMAIL PROTECTED] Arno Lehmann http://www.its-lehmann.de ------------------------------------------------------------------------- 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
