On Monday 26 February 2007 20:20, Rex Wheeler wrote: > > From: Alan Brown > > Sent: Monday, February 26, 2007 10:38 AM > > > > On Sat, 24 Feb 2007, Rex Wheeler wrote: > > > Does anyone know what kind of errors that the "VolErrors" column > > totals? > > > Primarily write errors and database vs tape file number mismatches > > > > Do you have the expertise to write something which can parse this > > information or would it need to go on the Bacula wishlist? > > I do have the expertise, but not sure about the time. It would be a > reasonable undertaking. It would involve: > > 1) Updating the storage daemon to send the appropriate SCSI commands to > inquire about error counts at mount and unmount times (or possibly with > each block read / write.)
I'm not ready to start putting SCSI commands into the Storage daemon. Maybe some day much later. > This shouldn't be too bad as the sg_logs > utility is out there and can access these statistics. The code could > either be pulled from that tool, or the storage daemon could just call > that tool and parse the results. Using an external program poses no problems. However, I suspect that the parsing should be done either in that program or in a script -- much the same way that mtx-changer is written. > > 2) Updating the configuration syntax and parser for the storage daemon > so the soft error recording logic could be enabled from the > configuration file. > > 3) Changing the protocol between the storage daemon and the director to > include the new soft error count information. > > 4) Changing the protocol between the director and the catalog service to > include the new soft error count information. > > 5) Changing the schema in the configuration store to hold this new > information. > > 6) Other stuff I haven't though of because I have only about an hour of > looking at the bacula source code. > > My initial plan in my spare time is to mess around with the SCSI stuff > in the storage engine and just send console messages back to the > director. If I can get that to work I may play with the other stuff. I > don't, however, take "playing with the other stuff" lightly. It involves > protocol and database changes and I have no idea what the procedure and > culture around here is for such things. The DIR-SD protocol and database changes are not very difficult. Some of important changes to maintain Device statistics are already being implemented at the moment by Eric. I think the missing pieces could be easily added either by Eric or myself at the appropriate time. > > Rex > > ------------------------------------------------------------------------- > 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 ------------------------------------------------------------------------- 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
