lsscsi-0.07 + scsi host information?
lsscsi is a utility the uses sysfs in kernels >= lk 2.5.50 to list information about all SCSI devices (including devices that use the SCSI stack such as USB mass storage devices). Both a compact format (default), one line per device, and a "classic" format (like the output of 'cat /proc/scsi/scsi') are supported.
Version 0.07 is available at
http://www.torque.net/scsi/lsscsi.html
In lk 2.5.60 the prefix to the "queue_depth" sysfs name was removed.
I would like lsscsi to list SCSI hosts (portals?) but there doesn't seem to be enough normalized sysfs information available to do that. Is the "/sys/class/scsi-host" sub-tree the place to be looking? Of the scsi hosts I have, only scsi_debug (thanks to work by Mike Anderson) puts an entry in that sub-tree. I would also like to have normalized information from the scsi_host structure available (similar to what Patrick Mansfield provided for scsi devices).
Doug Gilbert
Quoted 8 lines · Douglas Gilbert
I would like lsscsi to list SCSI hosts (portals?) but there doesn't seem to be enough normalized sysfs information available to do that. Is the "
/sys/class/scsi-host" sub-tree the place to be looking? Of the scsi hosts I have, onlyscsi_debug(thanks to work by Mike Anderson) puts an entry in that sub-tree. I would also like to have normalized information from thescsi_hoststructure available (similar to what Patrick Mansfield provided for scsi devices).
We could add scsi_host attributes under the same place as the scsi_host->host_gendev. But with sysfs, you could not tell if they were pci or scsi_host attributes.
We also need a place in sysfs for scsi core attributes - like max_scsi_luns, scsi_logging_level, max_scsi_report_luns, and maybe others, so they can be set and checked via /sysfs. But drivers under sysfs must (AFAIK) be on a "bus" and bind to devices on that same bus. For scsi core, we are more like a library, and do not have a specific type and set of devices to bind to.
-- Patrick Mansfield