Hello

I have (maybe similar?) problem with MD3620f (fibre channel array) and rhev(h) 3.1.

problem is that MD36xxf is not listed in default multipath configuration.

there was lots of errors in /var/log/messages

...
Apr 11 12:18:27 rhev-04 kernel: sd 6:0:1:4: [sdi] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00 Apr 11 12:18:28 rhev-04 multipathd: 36d4ae520006e702d0000054650579be9: sdl - directio checker reports path is down Apr 11 12:18:28 rhev-04 multipathd: 36d4ae520006e702d000003754f2aed00: sdm - directio checker reports path is down Apr 11 12:18:28 rhev-04 multipathd: 36d4ae520006e702d000003754f2aed00: sdj - directio checker reports path is down Apr 11 12:18:28 rhev-04 multipathd: 36d4ae520006e702d0000054650579be9: sdi - directio checker reports path is down Apr 11 12:18:29 rhev-04 kernel: sd 7:0:1:11: [sdn] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Apr 11 12:18:29 rhev-04 kernel: sd 7:0:1:11: [sdn] Sense Key : Illegal Request [current] Apr 11 12:18:29 rhev-04 kernel: sd 7:0:1:11: [sdn] <<vendor>> ASC=0x94 ASCQ=0x1ASC=0x94 ASCQ=0x1 Apr 11 12:18:29 rhev-04 kernel: sd 7:0:1:11: [sdn] CDB: Read(10): 28 00 00 00 00 00 00 00 04 00
...

I had to manually add this to /etc/multipath.conf

device {
     vendor "DELL"
     product "MD36xxf"
     product_blacklist "Universal Xport"
     path_grouping_policy group_by_prio
     getuid_callout "/lib/udev/scsi_id --whitelisted --device=/dev/%n"
     path_selector "round-robin 0"
     path_checker rdac
     features "2 pg_init_retries 50"
     hardware_handler "1 rdac"
     prio rdac
     failback immediate
     rr_weight uniform
     no_path_retry 15
     rr_min_io 1000
     rr_min_io_rq 1
}

after multipathd restart errors are gone and multipath works correctly

It would be nice to have this in default multipath config (at least for thin hypervisor)

btw. similar stuff on Dell's forum - http://en.community.dell.com/support-forums/storage/f/1216/t/19474086.aspx


bye, dron



Dne 12.4.2013 0:31, [email protected] napsal(a):
Hello J

Now I can say, that problem is not only in ovirt so firstly I would like
to try some tricks and tried to send report asap.

Thanks

*From:*Mark Wu [mailto:[email protected]]
*Sent:* Wednesday, April 10, 2013 3:33 AM
*To:* Kralicek, Martin
*Cc:* [email protected]
*Subject:* Re: [Users] oVirt 3.2 and MD3600i

On 04/10/2013 02:31 AM, [email protected]
<mailto:[email protected]> wrote:

    Hello,

    Has somebody experience with Dell MD3600i and oVirt 3.2.1?

    Host and oVirt are deployed on Fedora 18.

    My infrastructure contains: 2 x powerconnect 6224 and this storage
    with two controllers

    Both switch are in stack mode and storage is connect with four 10Gb
    ports in same subnet (is better to use it without stack as two subnet?)

    So, where is problem...I can create iSCSI storage domain, everything
    seems to be OK but when I want to add next host they cannot access
    this iSCSI target (in storage management tools is already added to
    host group)

    And during this process I can see only on host console IO error,
    buffer error and kernel BUG: soft lockup – CPU stuck etc...

Could you please paste the log messages related to the errors above ?

Exists recommended way how involved iSCSI?

Thanks for any suggestions

Martin

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

This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise confidential information. If you
have received it in error, please notify the sender immediately and
delete the original. Any other use of the e-mail by you is prohibited.

Where allowed by local law, electronic communications with Accenture and
its affiliates, including e-mail and instant messaging (including
content), may be scanned by our systems for the purposes of information
security and assessment of internal compliance with Accenture policy.

______________________________________________________________________________________

www.accenture.com <http://www.accenture.com>



_______________________________________________

Users mailing list

[email protected]  <mailto:[email protected]>

http://lists.ovirt.org/mailman/listinfo/users



_______________________________________________
Users mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/users


<<attachment: jiri_slezka.vcf>>

Attachment: smime.p7s
Description: Elektronicky podpis S/MIME

_______________________________________________
Users mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/users

Reply via email to