Kern: Would a simple test confirm/deny this?
i.e. tar a big random file onto the tape, filling it. i.e. erase the tape. Then try it with Bacula again. > On May 2, 2015, at 3:24 AM, Kern Sibbald <[email protected]> wrote: > > Dan, > > After a bit more thought, this reminds me of the bug we found in the FreeBSD > pthreads implementation about 10 years ago where they hit the end of the > logical tape (the end of tape marker) and return a -1, then instead of > letting Bacula write again, they continue to give it errors. > > The proper behavior at the logical end of tape when Bacula is writing return > a -1 status, then on the next write(s) allow them to succeed until the > physical end of tape is reached at which point it should always return a -1. > After Bacula gets the first -1 the only thing it does it to write an EOF mark > and attempt to backup and read the last block that was correctly written > (provided the standard Bacula Linux Device parameters are set). > > Best regards, > Kern > > On 01.05.2015 21:56, Kern Sibbald wrote: > > >> Hello Dan, >> >> - From what I see, the end of tape marker is missing or is too close to the >> physical end of the tape. I suspect that causes Bacula to write to the very >> physical end, and thus it cannot write the final EOF mark. Despite what >> Bacula says (it is being conservative) there is every chance that your tape >> is good. >> >> To know, you must restore the last file that was being written when the >> error occurred and see if it is correctly restored. >> >> Best regards, >> Kern >> >> On 01.05.2015 15:40, Dan Langille wrote: >> >> > I'm using Bacula 7.0.5 on FreeBSD 10.1 (bacula-dir) and FreeBSD 9.3 >> > (bacula-sd). >> >> > Sometimes I get dud tapes. Or at least, tapes my tape drive does not like. >> >> > For example: >> >> > ### >> > 01-May 09:39 crey-sd JobId 205441: End of Volume "FAI022" at 11:11326 on >> > device "DTL03" (/dev/nsa0). Write of 64512 bytes got 49152. >> > 01-May 09:39 crey-sd JobId 205441: Error: Error writing final EOF to tape. >> > This Volume may not be readable. >> > tape_dev.c:941 ioctl MTWEOF error on "DTL03" (/dev/nsa0). ERR=Input/output >> > error. >> > 01-May 09:39 crey-sd JobId 205441: End of medium on Volume "FAI022" >> > Bytes=10,784,406,528 Blocks=167,168 at 01-May-2015 09:39. >> > 01-May 09:39 crey-sd JobId 205441: 3307 Issuing autochanger "unload slot >> > 2, drive 0" command. >> > ### >> >> > See also, this from /var/log/messages: >> >> > ### >> > May 1 09:39:01 knew kernel: (sa0:sym0:0:1:0): WRITE FILEMARKS(6). CDB: 10 >> > 00 00 00 01 00 >> > May 1 09:39:01 knew kernel: (sa0:sym0:0:1:0): CAM status: SCSI Status >> > Error >> > May 1 09:39:01 knew kernel: (sa0:sym0:0:1:0): SCSI status: Check Condition >> > May 1 09:39:01 knew kernel: (sa0:sym0:0:1:0): SCSI sense: MEDIUM ERROR >> > asc:c,0 (Write error) >> > May 1 09:39:01 knew kernel: (sa0:sym0:0:1:0): Command Specific Info: >> > 0x28b4b >> > May 1 09:39:01 knew kernel: (sa0:sym0:0:1:0): Error 5, Retries exhausted >> > May 1 09:39:01 knew kernel: (sa0:sym0:0:1:0): WRITE FILEMARKS(6). CDB: 10 >> > 00 00 00 02 00 >> > May 1 09:39:01 knew kernel: (sa0:sym0:0:1:0): CAM status: SCSI Status >> > Error >> > May 1 09:39:01 knew kernel: (sa0:sym0:0:1:0): SCSI status: Check Condition >> > May 1 09:39:01 knew kernel: (sa0:sym0:0:1:0): SCSI sense: MEDIUM ERROR >> > asc:c,0 (Write error) >> > May 1 09:39:01 knew kernel: (sa0:sym0:0:1:0): Command Specific Info: >> > 0x28b4b >> > May 1 09:39:01 knew kernel: (sa0:sym0:0:1:0): Error 5, Retries exhausted >> > May 1 09:42:41 knew kernel: (sa0:sym0:0:1:0): WRITE FILEMARKS(6). CDB: 10 >> > 00 00 00 01 00 >> > May 1 09:42:41 knew kernel: (sa0:sym0:0:1:0): CAM status: SCSI Status >> > Error >> > May 1 09:42:41 knew kernel: (sa0:sym0:0:1:0): SCSI status: Check Condition >> > May 1 09:42:41 knew kernel: (sa0:sym0:0:1:0): SCSI sense: MEDIUM ERROR >> > asc:c,0 (Write error) >> > May 1 09:42:41 knew kernel: (sa0:sym0:0:1:0): Command Specific Info: >> > 0x11fb >> > May 1 09:42:41 knew kernel: (sa0:sym0:0:1:0): Error 5, Retries exhausted >> > May 1 09:42:41 knew kernel: (sa0:sym0:0:1:0): WRITE FILEMARKS(6). CDB: 10 >> > 00 00 00 02 00 >> > May 1 09:42:41 knew kernel: (sa0:sym0:0:1:0): CAM status: SCSI Status >> > Error >> > May 1 09:42:41 knew kernel: (sa0:sym0:0:1:0): SCSI status: Check Condition >> > May 1 09:42:41 knew kernel: (sa0:sym0:0:1:0): SCSI sense: MEDIUM ERROR >> > asc:c,0 (Write error) >> > May 1 09:42:41 knew kernel: (sa0:sym0:0:1:0): Command Specific Info: >> > 0x11fb >> > May 1 09:42:41 knew kernel: (sa0:sym0:0:1:0): Error 5, Retries exhausted >> > ### >> >> > In this case, I will mark the tape as DISABLED and once it is past it's >> > recycling date, I will retire the tape. >> >> > Best practice might be to rerun the backup, but this backup is also on >> > disk. >> >> > What do you usually do with tapes such as this? >> >> >> > — >> > Dan Langille >> > http://langille.org/ <http://langille.org/> >> >> >> >> >> >> >> >> > ------------------------------------------------------------------------------ >> > One dashboard for servers and applications across Physical-Virtual-Cloud >> > Widest out-of-the-box monitoring support with 50+ applications >> > Performance metrics, stats and reports that give you Actionable Insights >> > Deep dive visibility with transaction tracing using APM Insight. >> > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >> > <http://ad.doubleclick.net/ddm/clk/290420510;117567292;y> >> >> >> > _______________________________________________ >> > Bacula-users mailing list >> > [email protected] >> > <mailto:[email protected]> >> > https://lists.sourceforge.net/lists/listinfo/bacula-users >> > <https://lists.sourceforge.net/lists/listinfo/bacula-users> >> > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > One dashboard for servers and applications across > Physical-Virtual-Cloud > > > Widest out-of-the-box monitoring support with 50+ > applications > > > Performance metrics, stats and reports that give you > Actionable Insights > > > Deep dive visibility with transaction tracing using APM > Insight. > > > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > <http://ad.doubleclick.net/ddm/clk/290420510;117567292;y> > > > > > > > > > _______________________________________________ > > > Bacula-users mailing list > > > [email protected] > <mailto:[email protected]> > > > https://lists.sourceforge.net/lists/listinfo/bacula-users > <https://lists.sourceforge.net/lists/listinfo/bacula-users> > > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y_______________________________________________ > Bacula-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/bacula-users — Dan Langille http://langille <http://langille/>.org/
signature.asc
Description: Message signed with OpenPGP using GPGMail
------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
