> On May 20, 2015, at 3:37 AM, Kern Sibbald <k...@sibbald.com> wrote: > > Hello Dan, > > We recently discussed a problem with logical end of tape markers on the > newest FreeBSD system. That reminded me of the previous time we had > problems, and it took us a very long time to find the problem 3-4 months > if I remember right.
Thanks. I will try running that test ASAP, but I'm loaded up at present. The current situation arises on these second hand tapes I have obtained. The drive writes 200 or 300 MB to the tape and then the errors arise: Going back to a job which exhibits the problem: >> ### >> 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. >> ### I don't know enough about tape to comment, so I'm speculating. Could a previous use of this tape put an end of medium marker on the tape? FreeBSD sees this, reports it back to Bacula. Bacula says: No, thanks, I know what I'm doing, and continues to write data. FreeBSD says: no, no, you can't do this, I told you so... and everything stops. Is that probable? Likely? This is all moot until I run the test program. >> >> 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 >> ### > > Anyway, here is your email on the subject and the source of the file > that we used to diagnose the problem. I would be a bit surprised if the > current problem is the same thing, but it is probably worth trying. I > haven't tried compiling the program recently so let me know if you have > problems. > > Best regards, > Kern > > PS: It took me a long time to find these attachments because I thought > they were in the test environment, but it looks like I committed them to > the bacula/platforms/freebsd directory. > <pthreads-fix.txt><tapetest.c>------------------------------------------------------------------------------ > 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-devel mailing list > Bacula-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-devel — Dan 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-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
