All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: should the tur libchecker handle unit attention	conditions?
Date: Thu, 11 Oct 2007 08:06:38 +0200	[thread overview]
Message-ID: <470DBD6E.8010603@suse.de> (raw)
In-Reply-To: <1192031339.4086.37.camel@gator.sc.steeleye.com>

Eddie Williams wrote:
> I have noticed situations where paths bounce using the tur libchecker
> due to unit attention conditions.  Would there be any objection for
> attempting an automatic single retry in tur.c for a UA condition?
> 
No, please do. I've run into the same problems with the path_priority
callouts and will have to fix them, too.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)

      reply	other threads:[~2007-10-11  6:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-10 15:48 should the tur libchecker handle unit attention conditions? Eddie Williams
2007-10-11  6:06 ` Hannes Reinecke [this message]

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=470DBD6E.8010603@suse.de \
    --to=hare@suse.de \
    --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.