Bacula-users

[Bacula-users] Why bacula does not mark job as failed after "Write error" on tape drive?

2013-12-05 05:01:32
Subject: [Bacula-users] Why bacula does not mark job as failed after "Write error" on tape drive?
From: Andrey Lyarskiy <alyarskiy AT stacksoft DOT ru>
To: bacula-users AT lists.sourceforge DOT net
Date: Thu, 5 Dec 2013 13:34:10 +0400
Greetings! Recently I have noticed that all jobs status are fine,
independently of write errors on tape drive.

bacula.log:
05-Dec 07:27 backup-sd-office JobId 66089: Error: block.c:577 Write error at 
280:554 on device "Drive-0" (/dev/nst0). ERR=Input/output error.
05-Dec 07:27 backup-sd-office JobId 66089: Error: Error writing final EOF to 
tape. This Volume may not be readable.
dev.c:1557 ioctl MTWEOF error on "Drive-0" (/dev/nst0). ERR=Input/output error.
05-Dec 07:27 backup-sd-office JobId 66089: End of medium on Volume
"000842L5" Bytes=1,296,312,966,144 Blocks=20,094,136 at 05-Dec-2013
07:27.

TapeLibrary - IBM 3573-TL with LTO5 tapes.

Why bacula did not mark job #66089 as failed? IMHO after such error
all the jobs on this tape should be marked as possible-unreadable or
something like that.

------------------------------------------------------------------------------
Sponsored by Intel(R) XDK 
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users