Uploaded image for project: 'XenServer Org'
  1. XenServer Org
  2. XSO-772

Intel 82599 10Gb NIC max_sectors_kb

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 7.1
    • Fix Version/s: None
    • Component/s: Networking
    • Labels:
      None
    • Environment:

      Fujitsu Blade Server BX820_M2 with additional Mezzanine card added. The Mezzanine card add Intel 82599 10Gb nics for the blade. 

       

       

      Description

      kern.log errors:

      --------------------------------

      Jun  9 14:35:00 blade-server8 kernel: [14298.088668] sd 7:0:0:11: [sdb] tag#0 CDB: Read(10) 28 00 12 d1 95 90 00 05 10 00

      Jun  9 14:35:00 blade-server8 kernel: [14298.088671] blk_update_request: critical medium error, dev sdb, sector 315725200

      Jun  9 14:35:00 blade-server8 kernel: [14298.088697] blk_update_request: critical medium error, dev dm-1, sector 315725200

      Jun  9 14:35:01 blade-server8 kernel: [14299.091910] sd 7:0:0:11: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE

      Jun  9 14:35:01 blade-server8 kernel: [14299.091927] sd 7:0:0:11: [sdb] tag#0 Sense Key : Medium Error [current]

      Jun  9 14:35:01 blade-server8 kernel: [14299.091931] sd 7:0:0:11: [sdb] tag#0 Add. Sense: Unrecovered read error

      Jun  9 14:35:01 blade-server8 kernel: [14299.091935] sd 7:0:0:11: [sdb] tag#0 CDB: Read(10) 28 00 12 d1 95 90 00 05 10 00

      Jun  9 14:35:01 blade-server8 kernel: [14299.091938] blk_update_request: critical medium error, dev sdb, sector 315725200

      Jun  9 14:35:01 blade-server8 kernel: [14299.091955] blk_update_request: critical medium error, dev dm-1, sector 315725200

      Jun  9 14:35:02 blade-server8 kernel: [14300.080796] sd 7:0:0:11: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE

      Jun  9 14:35:02 blade-server8 kernel: [14300.080810] sd 7:0:0:11: [sdb] tag#0 Sense Key : Medium Error [current]

      --------------------------------

       

      XenServer 6.5 ran perfect. Upgraded to XenServer 7.1 and intel 82599's used for 10Gb connectivity to storage could access iSCSI LUN's, I could create my SR, I could even add a vdi and attach it to a VM. The problem was throughput. CrystalDiskMark on a Windows VM just returned an error since throughput was almost non-existent. Did many install/reinstalls and comparisons with 6.5/7.1 and found that max_sectors_kb was 512 for XenServer 6.5 and for some reason 1280 on XenServer 7.1. As soon as I changed max_sectors_kb for XenServer 7.1 all was well again for my 10Gb storage.

      I don't know what/how that setting gets assigned, I am assuming when an SR is created , but for my 82599's it was incorrectly set to 1280.

       

      -Alan-

       

        Attachments

          Activity

            People

            Assignee:
            matiasv Matias Vara Larsen
            Reporter:
            alantz Alan Lantz
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: