This may be fixed in 1.38, which is why I'm posting it here instead of to
the bugs page for the moment.
Over the easter break, our bacula system loaded in an unformatted LTO2
tape - which it thought was labelled.
Normally, if bacula believes the tape isn't labelled, it gets an io error,
proceeds to label it and then all is happy.
Because it believed the tape(volume) was already labelled, it got an IO
error, waited and then retried every 3 seconds, generating an email
message for every error
28,000+ error messages later, one of our older VMS machines (the one where
2 admins read mail) ran out of disk and got _very_ upset. Not long after
that, the main internal mailserver got clogged up with refusal and delayed
messages which were looping to that VMS box.
All in all "not very pleasant"....
What is current Bacula behaviour if it encounters a blank tape which it
believes is already labelled and how can a mailbomb be prevented if
someone else encounters this problem?
AB
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
