> I'm testing with tar on a new tape now. Should be a sufficient test since > the problems > occurs on all newly added tapes. I'm testing it on a different tapedrive now > since the > the full backup from the weekend is still running on the tapedrive in > question. I will > run it on the drive in question too, see if there is a difference. > > There are no errors in the bacula logs. I searched in the logs specifically > on the > volumes / tapes that were written with a insufficient amount of bytes and > some other > lines which might be suspect. > > However i do recall that there were occurences in which this error message > appeared > during labelling of new tapes some time back. It was not in the logs but i > remembered > some words and i think it was this one: (copied from the internet) > > block.c:994 Read error on fd=5 at file:blk 0:0 on device "Drive-1" > /dev/nst0). ERR=Input/output error. > 3000 OK label. VolBytes=64512 DVD=0 Volume="MSR100L3" Device="Drive-1" > (/dev/nst0) > This error is normal and will happen on most systems with never written tapes. The reason is if you read a tape that was never written the os returns an error. Since bacula always reads a volume to check the label before writing this error occurs. In the past there were a few discussions on whether or not to suppress the message in this case however for now it is still in.
John John ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
