From: Alan Kasindorf <akasindorf@mail.communityconnect.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: multipath-tools-0.4.4 on 3par unknown path failure issue
Date: Wed, 17 Aug 2005 15:38:38 -0400 [thread overview]
Message-ID: <4303923E.1000606@mail.communityconnect.com> (raw)
In-Reply-To: <42FBB2CC.2040508@mail.communityconnect.com>
I could use some suggestions on how to approach the issue at this
point... We're in a bad position because this bug did not come out
during a single instance test.
I have tried adjusting QLogic timeouts and any related parameters to see
if a higher or lower timeout would affect the issue at all, and it's
done nothing but make the problem worse.
I'm confident in what folks have said about 2.6.12 and later not
exhibiting this issue. However, I have a redhat kernel running Oracle,
and we need them to not drop our support. Currently redhat's support is
ignoring me as well. Should I talk with the QLogic maintainer at all?
3par has no clue, unless they're hiding their "Linux guy" from me.
Does SuSE professional have this patched up? We might be able to switch
to their distro if they will actually support multipathing on a database
in their mainline kernel, vs not at all.
Thanks,
-Alan
> We're running 2.6.9-11.ELsmp, off of redhat ES 4.1. I don't exactly have
> the entire list of redhat patches on hand, so I can't say for sure. Nor
> can I actually modify our kernel without losing support to the box. If
> this is fixed with a kernel upgrade, we can open a support ticket from
> redhat and scream/yell until they apply the patch.
next prev parent reply other threads:[~2005-08-17 19:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-10 21:49 multipath-tools-0.4.4 on 3par unknown path failure issue Alan Kasindorf
2005-08-11 19:55 ` Andy
2005-08-11 20:19 ` Alan Kasindorf
2005-08-12 16:04 ` Andy
2005-08-17 19:38 ` Alan Kasindorf [this message]
2005-08-17 20:08 ` Ed Wilts
2005-08-17 20:25 ` Alan Kasindorf
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=4303923E.1000606@mail.communityconnect.com \
--to=akasindorf@mail.communityconnect.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.