Linux Device Mapper development
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Losing paths
Date: Wed, 23 Jul 2008 08:25:01 +0200	[thread overview]
Message-ID: <4886CEBD.5090000@suse.de> (raw)
In-Reply-To: <48865AF2.8090000@actcom.co.il>

Hi Guy,

guy keren wrote:
> 
> Does the 'tur' checker take into account unit-attention issues (i.e. 
> when the configuration of a SCSI device changes, the next command coming 
> from an afected initiator (not necessarily to the same LU) should be 
> failed with a 'check condition' error and a 'unit attention' sense code.
> 
> if the TUR checker sent a TUR right after the change and before another 
> read/write command was sent - it will be failed, and then the question 
> is, whether the lower-level driver retries the TUR command, or returns 
> an error. any idea?
> 
It does for SLES10 SP2. Upstream not; I'll have to send the
patches one day.

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:[~2008-07-23  6:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-22 16:21 Losing paths Daniel Keisling
2008-07-22 22:10 ` guy keren
2008-07-23  6:25   ` Hannes Reinecke [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-08-26  7:33 Vardaris, C - SPLXM
2008-07-22 11:22 Vardaris, C - SPLXM
2008-07-22 14:44 ` Romanowski, John (OFT)
2008-07-22 14:55   ` Hannes Reinecke
2008-07-23  8:44   ` Vardaris, C - SPLXM
2008-07-23 12:33     ` Koehler, M - SPLXM
2008-07-23 13:12       ` Romanowski, John (OFT)
2008-07-23 13:22         ` Koehler, M - SPLXM
2008-07-23 17:00           ` Pradipmaya Maharana
2008-07-23 17:02           ` Romanowski, John (OFT)
2008-07-23 22:32             ` Menno Koehler

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=4886CEBD.5090000@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox