1. 23 8月, 2009 2 次提交
  2. 15 6月, 2009 1 次提交
  3. 10 6月, 2009 9 次提交
  4. 14 1月, 2009 1 次提交
  5. 17 12月, 2008 1 次提交
  6. 24 10月, 2008 1 次提交
  7. 27 7月, 2008 1 次提交
  8. 05 6月, 2008 1 次提交
  9. 27 5月, 2008 1 次提交
    • M
      [SCSI] fusion mpt: fix target missing after resetting external raid · 7ba2db5f
      Michael Reed 提交于
      Following a hard reset of a SAS raid, one of the raid targets is occasionally
      missing.  I tracked this down to a pretty obscure little bug.
      
      The LSI fusion drivers for SAS and Fibre Channel both use their respective
      transport layers.  Those transport layers increment the target number
      assigned to new targets.
      
      The routine __scsi_scan_target uses the "this_id" element of the Scsi_Host
      structure to avoid scanning the scsi host adapter.  Both fusion drivers set
      "this_id" from a value returned in a firmware PortFacts response.  For my
      particular test case (SAS) the firmware id assigned to the initiator was
      173.  After enough raid resets to cause the raid targets to go and come a
      sufficient number of times, the id assigned by the transport to a raid
      target would match the id assigned by the host adapter to the "this_id"
      field, resulting in that target not being scanned.
      
      Fix by not assigning this_id and not checking it in slave_configure. 
      Signed-off-by: NMichael Reed <mdr@sgi.com>
      Acked-by: N"Moore, Eric" <Eric.Moore@lsi.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@HansenPartnership.com>
      7ba2db5f
  10. 20 4月, 2008 1 次提交
  11. 08 4月, 2008 1 次提交
  12. 19 3月, 2008 1 次提交
  13. 04 3月, 2008 2 次提交
  14. 03 2月, 2008 1 次提交
  15. 24 1月, 2008 1 次提交
  16. 16 10月, 2007 2 次提交
  17. 13 10月, 2007 8 次提交
  18. 28 7月, 2007 1 次提交
  19. 19 7月, 2007 1 次提交
  20. 18 6月, 2007 3 次提交