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: Thu, 11 Aug 2005 16:19:24 -0400 [thread overview]
Message-ID: <42FBB2CC.2040508@mail.communityconnect.com> (raw)
In-Reply-To: <20050811195540.GA16665@thumper2>
> I've had problems like this happen to me on 3par too. What kernel version
> are you using? It almost always happened when the SAN got a RSCN (using
> when another server was rebooted) I found that, at least in kernel 2.6.11.7,
> that if I changed the line
>
> bio->bi_rw != (1 << BIO_RW_FAILFAST); to
> bio->bi_rw != (0 << BIO_RW_FAILFAST);
>
> in drivers/md/dm_mpath.c
>
> the problem went away. Now, in the newest kernels, after there was a big
> change to the qla drivers (2.6.12-rc? and beyond, I believe) I did not need
> to do the above change, but I now get aborts sometimes (these aborts
> apparently come from the qlogic card). The aborts recover, but I have been
> unable to determine why I am getting them.
>
> Andy
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.
However, I'd like to know what the exact issue is. I'm not exactly great
on eliciting issues with the linux kernel right now. How were you
monitoring what events the SAN was sending up through the card? I could
use this to at least verify what is happening if/when we lose another
mount. None of our servers were being rebooted when this happened though.
-Alan
next prev parent reply other threads:[~2005-08-11 20:19 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 [this message]
2005-08-12 16:04 ` Andy
2005-08-17 19:38 ` Alan Kasindorf
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=42FBB2CC.2040508@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.