All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH] HP SW support take 3
Date: Mon, 13 Jun 2005 19:24:27 -0500	[thread overview]
Message-ID: <42AE23BB.9040706@cs.wisc.edu> (raw)
In-Reply-To: <42AE220F.4090104@cs.wisc.edu>

Mike Christie wrote:
> Christophe Varoqui wrote:
> 
>> I confirm a robust behaviour now with take 3.
>> Here is a take 4 that move to an appropriate "best effort mode", ie 
>> always return success.
>>
>> The point is, whenever DM start submitting io the an asleep controler, 
>> precede with a START command. If it fails ... too bad, the consecutive 
>> io will fail and DM will try another PG. Had to do that because take 3 
>> interprets an error where the controler switch have correctly happened.
>>
> 
> ok so is it if the controller is already failed over and we send the 
> START command, rq->errors had some value so I ended up failing the 
> operation, right? Let me send a patch that will dump the sense and 
> rq->errors info out so we can see if there is some nice ASC/ASCQ value 
> that will tell us this occured like with the LSI boxes.

oh wait, when I reread this I guess you are saying that I was always 
gettting a rq->error value when I send a START_STOP and it succeeds?

  reply	other threads:[~2005-06-14  0:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-12 22:13 [PATCH] HP SW support take 3 Mike Christie
2005-06-13 13:10 ` Christophe Varoqui
2005-06-14  0:17   ` Mike Christie
2005-06-14  0:24     ` Mike Christie [this message]
2005-06-14  6:29       ` Christophe Varoqui

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=42AE23BB.9040706@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --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.