>>>> I see this I/O error after every label attempt.  Everything seems to be
>>>> fine, but I just want to know if this is expected behavior or anything
>>>> to watch out for.
>>> This will happen on every never written tape because you can not read
>>> a blank tape.
>> So it does happen, but in my opinion it should not happen.
>
> Unfortunately, there is no way to tell the difference between a tape which
> is genuinely blank, and a tape which contains data but has a bad block
> right at the beginning of the tape.
>
> The tape drive (most drives, anyway) will not differentiate; it will
> generate an identical "Media Error" sense code, in both cases.

Anyway, my point was that one could expect software to handle the raw error 
messages in a decent way, and only report an error to the user if the 
operation requested by the user, which in this case is labeling, fails for 
some reason (one of the reasons might be that tape already had a Bacula 
label). Providing reasonable amount of informative messages to the user is 
ok, but message saying "error" or especially  "i/o error" does not sound 
nice when there really is nothing wrong.

--
TiN 



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users