> Users tend to forget that in order for Bacula to label a tape, it > must first read the tape to ensure it is not destroying an already > labeled tape. > > If you try to read a perfectly blank tape, lots of ugly things happen. > > Thus you can avoid a lot of pains by *always* writing an EOF > mark at the beginning of a new tape. > Yes, when it's explained that way, it's quite logical. I've must been using some previously written tapes in the past, or I simply have neglected the error messge since I can't recall it.
It looks I'm not the only one who's been wondering this lately. Maybe it were possible to add some note about this into the label- command's error handling? It always looks bad when software reports about i/o error. I think that isn't mentioned in the manual either -not at least under "label console command" topic. -- TiN 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
