From: Jamie Bainbridge <jbainbri@redhat.com>
To: dm-devel@redhat.com
Subject: Bug 999761 - Review NetApp path_checker and features for RHEL5 mpath
Date: Mon, 2 Sep 2013 19:52:12 -0400 (EDT) [thread overview]
Message-ID: <1038339233.8389724.1378165932561.JavaMail.root@redhat.com> (raw)
Hi all,
I was wondering if I could get a response on this bug?
Bug 999761 - Review NetApp path_checker and features for RHEL5 mpath
https://bugzilla.redhat.com/show_bug.cgi?id=999761
In Bug 799842 NetApp requested that we change the default path_checker for NETAPP devices in RHEL 6.3 from directio to tur.
* Would we consider changing the default hwtable in RHEL5, considering it's in Production 2?
* Given NetApp reference the async tur improvements from Bug 760852 as part of their decision to use tur, is tur suitable for current RHEL5, or should we stick with directio?
* If tur is suitable for current RHEL5, should we change the default RHEL5 hwtable to use tur?
In Bug 799842 Comment 10 NetApp also requested we change the default features for NETAPP devices in RHEL 6.3 from "1 queue_if_no_path" to "3 queue_if_no_path pg_init_retries 50".
* pg_init_retries has been in RHEL5 since 5.2, is pg_init_retries suitable for current RHEL5 also? (this seems to be an easy "yes")
* If pg_init_retries is suitable for current RHEL5, should we change the default RHEL5 hwtable to use pg_init_retries?
Regards,
Jamie Bainbridge
Red Hat Asia Pacific
next reply other threads:[~2013-09-02 23:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 23:52 Jamie Bainbridge [this message]
2013-09-03 8:52 ` Bug 999761 - Review NetApp path_checker and features for RHEL5 mpath Martin George
2013-09-04 7:23 ` Jamie Bainbridge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1038339233.8389724.1378165932561.JavaMail.root@redhat.com \
--to=jbainbri@redhat.com \
--cc=dm-devel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).