SAS dual-path disk attaching problem (lsi hba with mpt2sas, lsi sas expanders)

Discussion in 'Linux Admins, Storage and Virtualization' started by Nurmaizer, Apr 30, 2018.

  1. Nurmaizer

    Nurmaizer New Member

    Joined:
    Apr 30, 2018
    Messages:
    1
    Likes Received:
    0
    Hello.

    Im using the following scheme for connecting 2 supermicro jbods to 2 hosts via minisas with 2 path for every sas disk:

    jbod_sheme.png

    All are working as expected: from every host i see every disk from all jbods for all sas expanders (front and back). But right now when im trying to attach new disk to the back side on the jbodB i see this disk only by the primary path on the hostB. I dont see this disk by the secondary path on the hostA.

    But i can see attached sas address of the disk on hostA via smp_discover:
    smp_discover -p $phys_num /dev/bsg/expander-$exp_num
    ...
    attached device type: end device
    negotiated logical link rate: phy enabled; 6 Gbps
    attached SAS address: 0x5000cca03.... (address the same as at hostB + 1)
    attached target: ssp=1 stp=0 smp=0 sata_device=0
    ...
    Discover response:
    phy identifier: $phys_num
    attached device type: end device
    negotiated logical link rate: phy enabled; 6 Gbps
    attached initiator: ssp=0 stp=0 smp=0 sata_host=0
    attached sata port selector: 0
    attached target: ssp=1 stp=0 smp=0 sata_device=0
    SAS address: 0x50030...
    attached SAS address: 0x5000cca03...
    attached phy identifier: 1
    programmed minimum physical link rate: 1.5 Gbps
    hardware minimum physical link rate: 1.5 Gbps
    programmed maximum physical link rate: 6 Gbps
    hardware maximum physical link rate: 6 Gbps
    phy change count: 6
    virtual phy: 0
    partial pathway timeout value: 7 us
    routing attribute: table
    connector type: SAS Drive backplane receptacle (SFF-8482) [max 2 phys]
    connector element index: 5
    connector physical link: 0

    But there is no any sas_port and block device for this phy in sysfs:
    ls -1 /sys/devices/$pci_bridge/$hba_pci_card/$host_num/$port_num/$front_expander_num/$front_expander_port_num/$back_expander_num/$phy_num/
    power
    sas_phy
    uevent

    Also if i poweroff/poweron jbodB i will see the disk by the secondary path on the hostA.

    So, the questions: why i see attached end_device and sas_address of it via phy but there is no sas_port for this phy and block device. How can i get block device without jbod power cycle? How can i debug this problem more deeper?

    Also i tried to check the disk via sas2ircu DISPLAY - it doesn't see attached disk too.
     
    #1
Similar Threads: dual-path disk
Forum Title Date
Linux Admins, Storage and Virtualization Which disks for new array? Aug 6, 2018
Linux Admins, Storage and Virtualization Formatting disks for ZFS on Linux May 8, 2018
Linux Admins, Storage and Virtualization VDO - disk compression and dedup for linux Apr 18, 2018
Linux Admins, Storage and Virtualization Getting SMART data from ZFS disks in Proxmox Mar 10, 2018
Linux Admins, Storage and Virtualization Interesting Proxmox Disk Usage Nov 12, 2017

Share This Page