going rogue: incorporating REPORT_LUNS into the SCSI probe
sequence
Matthew Jacob
mj at feral.com
Tue May 18 22:20:01 UTC 2010
I'm going to withdraw this- I've found a couple of bugs, and I think
it's important to actually deal with the case of no lun 0.
> This one is a bit rougher than the others, but I'd like to encourage
> some discussion about this.
>
> The problems presented by not using REPORT LUNS have been getting
> uglier and uglier. Any kind of sparse lun arrangement for large JBODs
> or RAID units just makes life very painful.
>
> These changes manage REPORT LUNS for devices > SPC2, and even manage
> changes in the list. These changes do *not* address the edge case of
> having no attached LUN 0 (which has been known to happen- it's not
> illegal).
>
> I haven't quite finished putting together an action based upon the LUN
> INVENTORY MAY HAVE CHANGED ASC/ASCQ, and testing has been somewhat light.
>
> Still......
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> freebsd-scsi at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-scsi
> To unsubscribe, send any mail to "freebsd-scsi-unsubscribe at freebsd.org"
More information about the freebsd-scsi
mailing list