Issue

• When the HITACHI GAD split over is performed from storage side, the 2 paths from local HITACHI SAN/Storage array are failed and /var/log/messages file gets flooded with following errors.

• With following flood of errors in logs the system becomes almost hung/unresponsive:

  Aug  1 10:00:10 testhost kernel: sd 0:0:0:0: [sda]  Sense Key : No Sense [current] 
  Aug  1 10:00:10 testhost kernel: sd 0:0:0:0: [sda]  Add. Sense: No additional sense information
  Aug  1 10:00:10 testhost kernel: sd 1:0:0:0: [sdd]  Sense Key : No Sense [current] 
  Aug  1 10:00:10 testhost kernel: sd 1:0:0:0: [sdd]  Add. Sense: No additional sense information
  Aug  1 10:00:10 testhost kernel: sd 0:0:0:0: [sda]  Sense Key : No Sense [current] 
  Aug  1 10:00:10 testhost kernel: sd 0:0:0:0: [sda]  Add. Sense: No additional sense information
  Aug  1 10:00:10 testhost kernel: sd 0:0:0:0: [sda]  Sense Key : No Sense [current] 
  Aug  1 10:00:10 testhost kernel: sd 0:0:0:0: [sda]  Add. Sense: No additional sense information
  Aug  1 10:00:10 testhost multipathd: base1: sdd - tur checker reports path is up
  Aug  1 10:00:10 testhost multipathd: 8:48: reinstated
  [...]
  

  These errors continues until the paths for local HITACHI SAN/Storage are restored from storage side.

• This issue does not occur on RHEL 5.11 release with identical HW/multipath configuration.