Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 31 Jul 2014 08:09:36 +0200
From:      Joerg Wunsch <freebsd-scsi@uriah.heep.sax.de>
To:        freebsd-scsi@freebsd.org
Cc:        "Kenneth D. Merry" <ken@FreeBSD.ORG>
Subject:   Re: Bacula fails on FreeBSD 10.x / "mt fsf" infinitely proceeds
Message-ID:  <20140731060936.GB4095@uriah.heep.sax.de>
In-Reply-To: <20140731035756.GA91452@nargothrond.kdm.org>
References:  <20140729224414.E2AAE276@uriah.heep.sax.de> <20140730035230.GA81800@nargothrond.kdm.org> <20140730060330.GA3272@uriah.heep.sax.de> <20140730153229.GA86368@nargothrond.kdm.org> <20140730191915.9B944267B@uriah.heep.sax.de> <20140730203315.0EED1295B@uriah.heep.sax.de> <20140730204200.4645729B8@uriah.heep.sax.de> <53D95F61.4080701@FreeBSD.org> <20140730215113.GA3564@uriah.heep.sax.de> <20140731035756.GA91452@nargothrond.kdm.org>

next in thread | previous in thread | raw e-mail | index | archive | help
As Kenneth D. Merry wrote:

> > SA_CCB_BUFFER_WAITING was indeed not tested anywhere else, but there
> > are decisions based on SA_CCB_BUFFER_IO (which used to be the opposite
> > of SA_CCB_BUFFER_WAITING).  These decisions now became random
> > decisions. :-(
> 
> Ahh, that explains it.

That's also what I thought then ... in particular, it explains why I
have seen one situation where the status has been reported correctly.

> 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.

> > Unfortunately, the new Bugzilla doesn't seem to accept me (I tried
> > Peter Wemm's description about kinit / kpasswd), so I cannot open
> > a bug report for it.

Meanwhile Eitan Adler helped me a bit, so the bug report is at:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192285

That way, it has been officially recorded, so we can take the time
needed for a real fix.

> > Attached is a suggested patch.  So far, I only compile-tested it.
> 
> As I said, I think it would be better to keep the ability to report both
> control and I/O errors.  If I have time tomorrow I'll try to come up with
> something.  (Or you can if you have the time.)

There's no longer any hurry on it now.  My patch^H^H^H^H^Hhack works,
Bacula could successfully write to the tape automatically for the
first time.  I'll try looking into an improved version, but I wouldn't
want to do too radical changes in order to not cause too much
potential for conflict in your other pending patches.
-- 
cheers, Joerg               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140731060936.GB4095>