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: Losing paths
Date: Tue, 22 Jul 2008 16:55:27 +0200	[thread overview]
Message-ID: <4885F4DF.8010000@suse.de> (raw)
In-Reply-To: <1D80D4F6D179BD4D869FE807A5BF833602D8B683@EXCNYSM0A1AN.nysemail.nyenet>

Hi John,

Romanowski, John (OFT) wrote:
> Hi,
> We had similar problem last year using sles9 and SVC 4.2.0.2,  as you describe: adding/deleting a LUN causes
> brief path failures for the host's remaining, unaffected LUNs.
> 
> We were using tur checker and it turned out that while adding/deleting a LUN (and some other admin tasks)
> the SVC does not respond well to test-unit-ready tur requests; but it responds perfectly well to normal read
> commands. I opened IBM PMR 43118 on that if you want to ask the SVC folks about it.  
> 
> Workaround for us was to use readsector0 instead of  tur as multipath path checker. 
>  
> Recent post here (see July 8, 2008)  said multipath-tools is deprecating readsector0, and to use directio as
> path checker, but directio was said to be much slower than tur, implying tur was better replacement than
> directio for readsector0. 
>
Only for those cases where no actual read-access is necessary.
 
> Not sure what deprecating readsector0 means for us SVC users.  
> 
It means you should be using directio there.

Thanks for the information, I'll see to have it included in SLES10.

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-22 14:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-22 11:22 Losing paths Vardaris, C - SPLXM
2008-07-22 14:44 ` Romanowski, John (OFT)
2008-07-22 14:55   ` Hannes Reinecke [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2008-07-22 16:21 Daniel Keisling
2008-07-22 22:10 ` guy keren
2008-07-23  6:25   ` Hannes Reinecke
2008-08-26  7:33 Vardaris, C - SPLXM

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=4885F4DF.8010000@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.