>> 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.
>>
>> Connecting to Storage daemon Sony SDX-700C at backup-va-1:9103 ...
>> Sending label command for Volume "000074" Slot 4 ...
>> 3307 Issuing autochanger "unload slot 3, drive 0" command.
>> 3304 Issuing autochanger "load slot 4, drive 0" command.
>> 3305 Autochanger "load slot 4, drive 0", status is OK.
>> block.c:999 Read error on fd=6 at file:blk 0:0 on device "Sony SDX-700C"
>> (/dev/rmt/0cn). ERR=I/O error.
>
> 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.
Yes, I know the technical explanation behind this message, but I find error 
messages like this more like "developer raw debugging messages" that might 
be enabled by some special flag on startup, but in my opinion error messages 
shown to user don't belong to expected succesful operation of any software. 
I think the proper behaviour of a mature software would be replacing these 
messages with something like "tape beginning with eof found" or "tape with 
no eof found". Error message should be shown only after a real error.

--
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