hpsa.txt 5.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131
  1. HPSA - Hewlett Packard Smart Array driver
  2. -----------------------------------------
  3. This file describes the hpsa SCSI driver for HP Smart Array controllers.
  4. The hpsa driver is intended to supplant the cciss driver for newer
  5. Smart Array controllers. The hpsa driver is a SCSI driver, while the
  6. cciss driver is a "block" driver. Actually cciss is both a block
  7. driver (for logical drives) AND a SCSI driver (for tape drives). This
  8. "split-brained" design of the cciss driver is a source of excess
  9. complexity and eliminating that complexity is one of the reasons
  10. for hpsa to exist.
  11. Supported devices:
  12. ------------------
  13. Smart Array P212
  14. Smart Array P410
  15. Smart Array P410i
  16. Smart Array P411
  17. Smart Array P812
  18. Smart Array P712m
  19. Smart Array P711m
  20. StorageWorks P1210m
  21. Additionally, older Smart Arrays may work with the hpsa driver if the kernel
  22. boot parameter "hpsa_allow_any=1" is specified, however these are not tested
  23. nor supported by HP with this driver. For older Smart Arrays, the cciss
  24. driver should still be used.
  25. The "hpsa_simple_mode=1" boot parameter may be used to prevent the driver from
  26. putting the controller into "performant" mode. The difference is that with simple
  27. mode, each command completion requires an interrupt, while with "performant mode"
  28. (the default, and ordinarily better performing) it is possible to have multiple
  29. command completions indicated by a single interrupt.
  30. HPSA specific entries in /sys
  31. -----------------------------
  32. In addition to the generic SCSI attributes available in /sys, hpsa supports
  33. the following attributes:
  34. HPSA specific host attributes:
  35. ------------------------------
  36. /sys/class/scsi_host/host*/rescan
  37. /sys/class/scsi_host/host*/firmware_revision
  38. /sys/class/scsi_host/host*/resettable
  39. /sys/class/scsi_host/host*/transport_mode
  40. the host "rescan" attribute is a write only attribute. Writing to this
  41. attribute will cause the driver to scan for new, changed, or removed devices
  42. (e.g. hot-plugged tape drives, or newly configured or deleted logical drives,
  43. etc.) and notify the SCSI midlayer of any changes detected. Normally this is
  44. triggered automatically by HP's Array Configuration Utility (either the GUI or
  45. command line variety) so for logical drive changes, the user should not
  46. normally have to use this. It may be useful when hot plugging devices like
  47. tape drives, or entire storage boxes containing pre-configured logical drives.
  48. The "firmware_revision" attribute contains the firmware version of the Smart Array.
  49. For example:
  50. root@host:/sys/class/scsi_host/host4# cat firmware_revision
  51. 7.14
  52. The transport_mode indicates whether the controller is in "performant"
  53. or "simple" mode. This is controlled by the "hpsa_simple_mode" module
  54. parameter.
  55. The "resettable" read-only attribute indicates whether a particular
  56. controller is able to honor the "reset_devices" kernel parameter. If the
  57. device is resettable, this file will contain a "1", otherwise, a "0". This
  58. parameter is used by kdump, for example, to reset the controller at driver
  59. load time to eliminate any outstanding commands on the controller and get the
  60. controller into a known state so that the kdump initiated i/o will work right
  61. and not be disrupted in any way by stale commands or other stale state
  62. remaining on the controller from the previous kernel. This attribute enables
  63. kexec tools to warn the user if they attempt to designate a device which is
  64. unable to honor the reset_devices kernel parameter as a dump device.
  65. HPSA specific disk attributes:
  66. ------------------------------
  67. /sys/class/scsi_disk/c:b:t:l/device/unique_id
  68. /sys/class/scsi_disk/c:b:t:l/device/raid_level
  69. /sys/class/scsi_disk/c:b:t:l/device/lunid
  70. (where c:b:t:l are the controller, bus, target and lun of the device)
  71. For example:
  72. root@host:/sys/class/scsi_disk/4:0:0:0/device# cat unique_id
  73. 600508B1001044395355323037570F77
  74. root@host:/sys/class/scsi_disk/4:0:0:0/device# cat lunid
  75. 0x0000004000000000
  76. root@host:/sys/class/scsi_disk/4:0:0:0/device# cat raid_level
  77. RAID 0
  78. HPSA specific ioctls:
  79. ---------------------
  80. For compatibility with applications written for the cciss driver, many, but
  81. not all of the ioctls supported by the cciss driver are also supported by the
  82. hpsa driver. The data structures used by these are described in
  83. include/linux/cciss_ioctl.h
  84. CCISS_DEREGDISK
  85. CCISS_REGNEWDISK
  86. CCISS_REGNEWD
  87. The above three ioctls all do exactly the same thing, which is to cause the driver
  88. to rescan for new devices. This does exactly the same thing as writing to the
  89. hpsa specific host "rescan" attribute.
  90. CCISS_GETPCIINFO
  91. Returns PCI domain, bus, device and function and "board ID" (PCI subsystem ID).
  92. CCISS_GETDRIVVER
  93. Returns driver version in three bytes encoded as:
  94. (major_version << 16) | (minor_version << 8) | (subminor_version)
  95. CCISS_PASSTHRU
  96. CCISS_BIG_PASSTHRU
  97. Allows "BMIC" and "CISS" commands to be passed through to the Smart Array.
  98. These are used extensively by the HP Array Configuration Utility, SNMP storage
  99. agents, etc. See cciss_vol_status at http://cciss.sf.net for some examples.