All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy <genanr@emsphone.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 14:55:40 -0500	[thread overview]
Message-ID: <20050811195540.GA16665@thumper2> (raw)
In-Reply-To: <42FA7674.4070201@mail.communityconnect.com>

On Wed, Aug 10, 2005 at 05:49:40PM -0400, Alan Kasindorf wrote:
> Hey,
> 
> 
> At some random point in time today, one of the machines lost one of its 
> four 3par mounts. All other mounts worked fine. This has happened once 
> or twice before as well, but we rebooted before I had time to inspect 
> the issue.
> 
> Is this known at all? Is there anything else I can provide so that we 
> can figure out why this happened? I had been running multipath tools for 
> two months on a test box and never encounterred this problem. It's only 
> snuck up as we've started deploying it on more machines for 
>
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

  reply	other threads:[~2005-08-11 19:55 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 [this message]
2005-08-11 20:19   ` Alan Kasindorf
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=20050811195540.GA16665@thumper2 \
    --to=genanr@emsphone.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.