Bacula fails on FreeBSD 10.x / "mt fsf" infinitely proceeds

[Joerg Wunsch]

As Joerg Wunsch wrote:

> > I think it would be good to keep the ability to report to the application
> > or the user what happened with control and data commands, especially since
> > you may wind up having errors on both types of commands in some cases. 
> > (e.g. end of media notification on a write, and then perhaps an issue in
> > writing the filemarks.)
> 
> OK, then it needs some more work.

Next attempt: in saerror(), rather than basing the decision whether
this status report belongs to a read/write or control operation on
some CCB flag that needs to be set explicitly, base it on the actual
command that led to the status report (SA_READ or SA_WRITE
vs. anything else).  A similar decision is already done in saerror().

I think this keeps the spirit of the existing implementation as much as
possible.

So far, only compile-tested.
-- 
cheers, Joerg               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: scsi_sa.c.diff
Type: text/x-diff
Size: 5515 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-scsi/attachments/20140731/d90343d5/attachment.diff>