Hello, I was about to write to you based on your first email containing only the error that tape errors should be extremely rare and even non-existent. The exception is when tapes fill, the information that Bacula gets depends on the tape drive. In from what I see below, as already commented by others, this seems to be a somewhat normal "end of tape" condition, where Bacula receives a return indicating that the block was not written. Unfortunately, the error it gets is generally not distinguishable from an end of tape condition. In that case it then writes an end of file mark and attempts to re-read the last good block. If it succeeds as it did in your case, there is probably a 99.999% chance that the tape is perfectly valid.
The only other thing to check is to see if the amount of data that was written on the volume corresponds roughly to what you expect -- generally there is a 2/1 compression done by the tape drive, but that is rather general it can vary from 1/1 (already compressed data) to 3/1 for pure text. Best regards, Kern On 09/05/2014 10:12 PM, Stephen Thompson wrote: > Huh, maybe this is a misdiagnosis of the end of tape and a write error > only in the sense that there is no tape left. > > 05-Sep 00:41 SD_L100_ JobId 389348: Error: block.c:255 Write error at > 610:412 on device "L100-Drive-0" (/dev/L100-Drive-0). ERR=Input/output > error. > 05-Sep 00:41 SD_L100_ JobId 389348: Re-read of last block succeeded. > 05-Sep 00:41 SD_L100_ JobId 389348: End of medium on Volume "IM0161" > Bytes=1,090,307,051,520 Blocks=520,103 at 05-Sep-2014 00:41. > > > On 09/05/2014 09:42 AM, Stephen Thompson wrote: >> Hello, >> >> I sporadically get these types of alerts for one on my bacula tape >> libraries... >> >> 05-Sep 00:41 lawson-sd_L100_ JobId 389348: Error: block.c:255 Write >> error at 610:412 on device "L100-Drive-0" (/dev/L100-Drive-0). >> ERR=Input/output error. >> >> Am I correct in assuming that this was indeed a tape write error, but >> that bacula will attempt a 2nd write of the same block of data and if >> that 2nd attempt succeeds proceed on and ultimately have a successfully >> run job (one that can be restored without issue)? >> >> In other words, should this error worry me if it doesn't happen often? >> It does consistently happen -- with 100's of jobs a night, it probably >> happens 3-4 times a week. >> >> thanks, >> Stephen >> >> >> ------------------------------------------------------------------------------ >> Slashdot TV. >> Video for Nerds. Stuff that matters. >> http://tv.slashdot.org/ >> _______________________________________________ >> Bacula-users mailing list >> Bacula-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/bacula-users >> > ------------------------------------------------------------------------------ > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
