/dev/ch0 not recognized

[Matthew Jacob]

The REPORT_LUNS changes specifically excludes any addressing types other 
than PERIPH or FLAT precisely because it is unknown how CAM should 
represent it. Does CISS report another type in REPORT_LUNS?

It is conceivable to retain a u_int for luns and apply some kind of 
predictable transform on other addressing types. Whether this is a hack, 
or recognizing that other addressing types are practically nonexistent 
is a matter for debate.

> Yeah, that's what I get for keeping track of too many raid drivers in my head without looking closely at the code from time to time.  The trick with CISS is that it advertises extended LUNs, which CAM really doesn't understand.  There are two problems.  The first is that LUN addressing in CAM is restricted to a u_int, which cannot reliably hold the extended LUN space on all platforms.  The second is that, until recently, it was not feasible to search the extended LUN space (or even the traditional LUN space).  Matt Jacob's REPORT_LUNS work might help with this, assuming that the CISS controller will respond to such commands.  That's worth looking into.  But even if it does, the limited definition of a LUN in CAM is going to be problematic; it can be hacked to just ignore the problem, but it would be nice to fix it correctly.
>
> Scott
>
>
> _______________________________________________
> 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"
>