hpsa.txt 3.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100
  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. HPSA specific entries in /sys
  26. -----------------------------
  27. In addition to the generic SCSI attributes available in /sys, hpsa supports
  28. the following attributes:
  29. HPSA specific host attributes:
  30. ------------------------------
  31. /sys/class/scsi_host/host*/rescan
  32. the host "rescan" attribute is a write only attribute. Writing to this
  33. attribute will cause the driver to scan for new, changed, or removed devices
  34. (e.g. hot-plugged tape drives, or newly configured or deleted logical drives,
  35. etc.) and notify the SCSI midlayer of any changes detected. Normally this is
  36. triggered automatically by HP's Array Configuration Utility (either the GUI or
  37. command line variety) so for logical drive changes, the user should not
  38. normally have to use this. It may be useful when hot plugging devices like
  39. tape drives, or entire storage boxes containing pre-configured logical drives.
  40. HPSA specific disk attributes:
  41. ------------------------------
  42. /sys/class/scsi_disk/c:b:t:l/device/unique_id
  43. /sys/class/scsi_disk/c:b:t:l/device/raid_level
  44. /sys/class/scsi_disk/c:b:t:l/device/lunid
  45. (where c:b:t:l are the controller, bus, target and lun of the device)
  46. For example:
  47. root@host:/sys/class/scsi_disk/4:0:0:0/device# cat unique_id
  48. 600508B1001044395355323037570F77
  49. root@host:/sys/class/scsi_disk/4:0:0:0/device# cat lunid
  50. 0x0000004000000000
  51. root@host:/sys/class/scsi_disk/4:0:0:0/device# cat raid_level
  52. RAID 0
  53. HPSA specific ioctls:
  54. ---------------------
  55. For compatibility with applications written for the cciss driver, many, but
  56. not all of the ioctls supported by the cciss driver are also supported by the
  57. hpsa driver. The data structures used by these are described in
  58. include/linux/cciss_ioctl.h
  59. CCISS_DEREGDISK
  60. CCISS_REGNEWDISK
  61. CCISS_REGNEWD
  62. The above three ioctls all do exactly the same thing, which is to cause the driver
  63. to rescan for new devices. This does exactly the same thing as writing to the
  64. hpsa specific host "rescan" attribute.
  65. CCISS_GETPCIINFO
  66. Returns PCI domain, bus, device and function and "board ID" (PCI subsystem ID).
  67. CCISS_GETDRIVVER
  68. Returns driver version in three bytes encoded as:
  69. (major_version << 16) | (minor_version << 8) | (subminor_version)
  70. CCISS_PASSTHRU
  71. CCISS_BIG_PASSTHRU
  72. Allows "BMIC" and "CISS" commands to be passed through to the Smart Array.
  73. These are used extensively by the HP Array Configuration Utility, SNMP storage
  74. agents, etc. See cciss_vol_status at http://cciss.sf.net for some examples.