qla2xxx Abort command issued nexus=1:0:1 after reboot with the new 4.18 kernel

    • OMV 4.x
    • Update

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • qla2xxx Abort command issued nexus=1:0:1 after reboot with the new 4.18 kernel

      I'm running OMV 4.1.14.-1.
      After upgrading and rebooting (there were new packages in Update Management) I noticed that disks connected to the QLA200 FC adapter are getting disconnected after some time.
      Without load it takes a couple of hours, with load a couple of minutes.
      This happens with the new kernel 4.18.0-0.bpo1-amd64, when I reboot using the old kernel 4.14.0-0.bpo3-amd64 then there is no problem even under heavy load.
      Here are a couple of lines from the log:

      Source Code

      1. Nov 28 13:28:59 instalacky kernel: [ 518.876602] qla2xxx [0000:09:04.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
      2. Nov 28 13:29:12 instalacky kernel: [ 531.940596] qla2xxx [0000:09:04.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
      3. Nov 28 13:29:43 instalacky kernel: [ 562.152316] qla2xxx [0000:09:04.0]-8009:2: DEVICE RESET ISSUED nexus=2:0:1 cmd=00000000d4913229.
      4. Nov 28 13:29:43 instalacky kernel: [ 562.152547] qla2xxx [0000:09:04.0]-800e:2: DEVICE RESET SUCCEEDED nexus:2:0:1 cmd=00000000d4913229.
      5. Nov 28 13:30:13 instalacky kernel: [ 593.080092] qla2xxx [0000:09:04.0]-8009:2: TARGET RESET ISSUED nexus=2:0:1 cmd=00000000d4913229.
      6. Nov 28 13:30:13 instalacky kernel: [ 593.080362] qla2xxx [0000:09:04.0]-800f:2: TARGET RESET FAILED: Task management failed nexus=2:0:1 cmd=00000000d4913229.
      7. Nov 28 13:30:13 instalacky kernel: [ 593.080368] qla2xxx [0000:09:04.0]-8012:2: BUS RESET ISSUED nexus=2:0:1.
      8. Nov 28 13:30:23 instalacky kernel: [ 603.096062] sd 2:0:0:1: [sde] tag#3553 FAILED Result: hostbyte=DID_TRANSPORT_DISRUPTED driverbyte=DRIVER_OK
      9. Nov 28 13:30:23 instalacky kernel: [ 603.096069] sd 2:0:0:1: [sde] tag#3553 CDB: Read(16) 88 00 00 00 00 00 6e 2a be 50 00 00 01 00 00 00
      10. Nov 28 13:30:23 instalacky kernel: [ 603.096292] sd 2:0:0:1: [sde] tag#3552 FAILED Result: hostbyte=DID_TRANSPORT_DISRUPTED driverbyte=DRIVER_OK
      11. Nov 28 13:30:23 instalacky kernel: [ 603.096297] sd 2:0:0:1: [sde] tag#3552 CDB: Read(16) 88 00 00 00 00 00 6e 2a bf 50 00 00 01 00 00 00
      12. Nov 28 13:30:24 instalacky kernel: [ 603.186754] scsi 2:0:0:0: Direct-Access DGC RAID 5 0219 PQ: 0 ANSI: 4
      13. Nov 28 13:30:24 instalacky kernel: [ 603.187746] sd 2:0:0:0: Power-on or device reset occurred
      14. Nov 28 13:30:24 instalacky kernel: [ 603.188045] sd 2:0:0:0: Attached scsi generic sg5 type 0
      15. Nov 28 13:30:24 instalacky kernel: [ 603.193311] sd 2:0:0:0: [sdf] 1367343104 512-byte logical blocks: (700 GB/652 GiB)
      16. Nov 28 13:30:24 instalacky kernel: [ 603.193990] sd 2:0:0:0: [sdf] Write Protect is off
      17. Nov 28 13:30:24 instalacky kernel: [ 603.194221] scsi 2:0:0:1: Direct-Access DGC RAID 5 0219 PQ: 0 ANSI: 4
      18. Nov 28 13:30:24 instalacky kernel: [ 603.195064] sd 2:0:0:0: [sdf] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
      19. Nov 28 13:30:24 instalacky kernel: [ 603.195796] sd 2:0:0:1: Attached scsi generic sg6 type 0
      20. Nov 28 13:30:24 instalacky kernel: [ 603.196268] sd 2:0:0:1: Power-on or device reset occurred
      21. Nov 28 13:30:24 instalacky kernel: [ 603.196980] sd 2:0:0:1: [sdg] Very big device. Trying to use READ CAPACITY(16).
      22. Nov 28 13:30:24 instalacky kernel: [ 603.197718] sd 2:0:0:1: [sdg] 6729760768 512-byte logical blocks: (3.45 TB/3.13 TiB)
      23. Nov 28 13:30:24 instalacky kernel: [ 603.197929] sd 2:0:0:1: [sdg] Write Protect is off
      24. Nov 28 13:30:24 instalacky kernel: [ 603.198367] sd 2:0:0:1: [sdg] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
      25. Nov 28 13:30:24 instalacky kernel: [ 603.200212] sd 2:0:0:1: [sdg] Very big device. Trying to use READ CAPACITY(16).
      26. Nov 28 13:30:24 instalacky kernel: [ 603.203229] sd 2:0:0:0: [sdf] Attached SCSI disk
      27. Nov 28 13:30:24 instalacky kernel: [ 603.229884] sd 2:0:0:1: [sdg] Very big device. Trying to use READ CAPACITY(16).
      28. Nov 28 13:30:24 instalacky kernel: [ 603.230946] sd 2:0:0:1: [sdg] Attached SCSI disk
      29. Nov 28 13:30:28 instalacky kernel: [ 608.113842] EXT4-fs warning (device md0): htree_dirblock_to_tree:978: inode #146080612: lblock 0: comm smbd: error -5 reading directory block
      30. Nov 28 13:30:28 instalacky kernel: [ 608.119039] EXT4-fs warning (device md0): htree_dirblock_to_tree:978: inode #146080612: lblock 0: comm smbd: error -5 reading directory block
      31. Nov 28 13:30:29 instalacky kernel: [ 608.541402] EXT4-fs warning (device md0): htree_dirblock_to_tree:978: inode #146080612: lblock 0: comm smbd: error -5 reading directory block
      32. Nov 28 13:30:29 instalacky kernel: [ 608.598291] EXT4-fs warning (device md0): htree_dirblock_to_tree:978: inode #146080612: lblock 0: comm smbd: error -5 reading directory block
      33. Nov 28 13:30:29 instalacky kernel: [ 608.606456] EXT4-fs warning (device md0): htree_dirblock_to_tree:978: inode #146080612: lblock 0: comm smbd: error -5 reading directory block
      34. Nov 28 13:30:55 instalacky kernel: [ 634.654211] EXT4-fs warning (device md0): htree_dirblock_to_tree:978: inode #146080612: lblock 0: comm smbd: error -5 reading directory block
      35. Nov 28 13:32:06 instalacky kernel: [ 705.732598] EXT4-fs warning (device md0): htree_dirblock_to_tree:978: inode #147522483: lblock 0: comm rsync: error -5 reading directory block
      36. Nov 28 13:32:06 instalacky kernel: [ 705.732719] EXT4-fs warning (device md0): htree_dirblock_to_tree:978: inode #147522431: lblock 0: comm rsync: error -5 reading directory block
      37. Nov 28 13:32:06 instalacky kernel: [ 705.732784] EXT4-fs warning (device md0): htree_dirblock_to_tree:978: inode #147522429: lblock 0: comm rsync: error -5 reading directory block
      38. Nov 28 13:32:06 instalacky kernel: [ 705.732863] EXT4-fs warning (device md0): htree_dirblock_to_tree:978: inode #147522427: lblock 0: comm rsync: error -5 reading directory block
      39. Nov 28 13:32:06 instalacky kernel: [ 705.732925] EXT4-fs warning (device md0): htree_dirblock_to_tree:978: inode #147522425: lblock 0: comm rsync: error -5 reading directory block
      40. Nov 28 13:32:06 instalacky kernel: [ 705.732986] EXT4-fs warning (device md0): htree_dirblock_to_tree:978: inode #147522418: lblock 0: comm rsync: error -5 reading directory block
      41. Nov 28 13:32:06 instalacky kernel: [ 705.733064] EXT4-fs warning (device md0): htree_dirblock_to_tree:978: inode #146604637: lblock 0: comm rsync: error -5 reading directory block
      42. Nov 28 13:32:06 instalacky kernel: [ 705.733140] EXT4-fs warning (device md0): htree_dirblock_to_tree:978: inode #146604611: lblock 0: comm rsync: error -5 reading directory block
      43. Nov 28 13:32:06 instalacky kernel: [ 705.733202] EXT4-fs warning (device md0): htree_dirblock_to_tree:978: inode #146606851: lblock 0: comm rsync: error -5 reading directory block
      44. Nov 28 13:32:06 instalacky kernel: [ 705.733263] EXT4-fs warning (device md0): htree_dirblock_to_tree:978: inode #146604133: lblock 0: comm rsync: error -5 reading directory block
      45. Nov 28 13:32:07 instalacky kernel: [ 705.809550] PGD 0 P4D 0
      46. Nov 28 13:32:07 instalacky kernel: [ 705.817289] Oops: 0000 [#1] SMP PTI
      Display All

      Is it possible that there is a different qla2xxx driver version in the new kernel?
      How do I fix this, I don't want to stay on the 4.18.0-0.bpo1-amd64 kernel ...