[patch] CTL should check condition INQUIRY with invalid LUN
Kenneth D. Merry
ken at freebsd.org
Wed Mar 7 22:47:16 UTC 2012
On Wed, Mar 07, 2012 at 14:40:05 -0800, Chuck Tuffli wrote:
> On Wed, Mar 7, 2012 at 2:25 PM, Kenneth D. Merry <ken at freebsd.org> wrote:
> > On Wed, Mar 07, 2012 at 14:17:14 -0800, Chuck Tuffli wrote:
> >> On Wed, Mar 7, 2012 at 12:22 PM, Kenneth D. Merry <ken at freebsd.org> wrote:
> >> > On Tue, Mar 06, 2012 at 16:30:22 -0800, Chuck Tuffli wrote:
> >> ...
> >> >> Linux does issue REPORT LUNs, but most of the time, this gets
> >> >> check-conditioned with illegal request, overlapped commands attempted.
> >> >
> >> > Hmm, that sounds suspicious. ?What is the exact ASC/ASCQ reported?
> >> >
> >> > Are you setting the tag_action field in the ATIO that gets sent to CTL?
> >> > Only one untagged command is allowed at a time.
> >> Ooops, no I wasn't. Fixed that and the illegal request check condition
> >> has gone away (tnx!)
> > Ahh, cool. ?So is Linux probing things properly now?
> No, the probing is messed up unless I change the inquiry device
> qualifier/type to 0x3/0x1f, but the spurious check conditions are now
So that means it is sending a REPORT LUNS, but ignoring the results?
If it were using the results to decide which LUNs to probe, then it
wouldn't be sending inquiry commands to unsupported LUNs.
ken at FreeBSD.ORG
More information about the freebsd-scsi