Getting DID_REQUEUE errors on SAN devices

Issue

• Getting DID_REQUEUE errors on SAN devices.

• RHEL servers showing multipath path failures with following errors:

  kernel: sd 1:0:3:80: [sdaih] tag#5 FAILED Result: hostbyte=DID_REQUEUE driverbyte=DRIVER_OK cmd_age=61s
  kernel: sd 1:0:3:80: [sdaih] tag#5 CDB: Test Unit Ready 00 00 00 00 00 00
  kernel: sd 1:0:1:80: [sdnt] tag#4 FAILED Result: hostbyte=DID_REQUEUE driverbyte=DRIVER_OK cmd_age=31s
  kernel: sd 1:0:1:80: [sdnt] tag#4 CDB: Test Unit Ready 00 00 00 00 00 00
  kernel: sd 1:0:3:134: [sdamk] tag#9 FAILED Result: hostbyte=DID_REQUEUE driverbyte=DRIVER_OK cmd_age=30s
  kernel: sd 1:0:3:134: [sdamk] tag#9 CDB: Test Unit Ready 00 00 00 00 00 00
  [...]
  multipathd: mpatha: sdnt - tur checker reports path is down
  kernel: device-mapper: multipath: Failing path 71:496.
  checker failed path 71:496 in map mpatha
  multipathd: mpatha: remaining active paths: 6
  [...]