All of lore.kernel.org
 help / color / mirror / Atom feed
From: christophe varoqui <christophe.varoqui@free.fr>
To: Eddie Williams <Eddie.Williams@Steeleye.com>
Cc: device-mapper development <dm-devel@redhat.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [dm-devel] [multipath] SCSI device capacity mess
Date: Wed, 27 Oct 2004 22:19:06 +0200	[thread overview]
Message-ID: <1098908346.12464.44.camel@zezette> (raw)
In-Reply-To: <1098905875.4472.92.camel@gator.sc.steeleye.com>


> Switching LUNs from one path to another is not a fast process and if
> this happens during periods of heaving IO periods, significant thrashing
> can result.
> 
> I think if we want to play at the Enterprise level where there are many
> servers connected up to large arrays I don't think it is a good idea to
> knowingly cause disruptions to others on the SAN.  Causing LUNs to
> switch from one path to another is such a behavior.
> 
I certainly don't militate for the NOSTARTONADD flag removal for all
devices. I just consider it annoying for the HSG80 / HSV* family
controlers :

- Either they are in failover mode and there is no bouncing possible, so
start_stop is harmless

- Either they are in multibus mode, then not sending start_stop before
READ CAPA lead to cmd failure and wrong size stored. Hence ghosts path
are ununsable even when they come up. [Here, I shamely hide the
device-mapper hooks on path activation could work]

- Either way, these controler families are *not* high-end devices,
whatever the criteria (capacity, throughput, cache, alarming, ...). The
whole ghost-path notion being the best evidence.

regards,
-- 
christophe varoqui <christophe.varoqui@free.fr>


  reply	other threads:[~2004-10-27 20:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-26 23:27 [multipath] SCSI device capacity mess christophe varoqui
2004-10-26 21:34 ` James Bottomley
2004-10-26 21:46   ` christophe varoqui
2004-10-27  8:17 ` [dm-devel] " Lars Marowsky-Bree
2004-10-27  8:42   ` Lars Marowsky-Bree
2004-10-27 18:51     ` Bryan Henderson
2004-10-29 14:12       ` Lars Marowsky-Bree
2004-10-29 16:48         ` Bryan Henderson
2004-10-27 19:02   ` christophe varoqui
2004-10-27 19:37     ` Eddie Williams
2004-10-27 20:19       ` christophe varoqui [this message]
2004-10-27 20:34         ` Greg Freemyer
2004-10-27 20:28     ` Philip R Auld
2004-10-27 21:57     ` James Bottomley
2004-10-28 11:37       ` Lars Marowsky-Bree
2004-10-28 18:14         ` Patrick Mansfield
2004-10-28 18:21           ` Lars Marowsky-Bree
2004-10-30  0:41             ` Patrick Mansfield
2004-10-30  1:01               ` Patrick Mansfield
2004-10-30  7:21               ` christophe varoqui
2004-10-30  8:22                 ` christophe varoqui
2004-11-02 15:23                 ` Lars Marowsky-Bree
2004-10-28 11:35     ` Lars Marowsky-Bree

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=1098908346.12464.44.camel@zezette \
    --to=christophe.varoqui@free.fr \
    --cc=Eddie.Williams@Steeleye.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-scsi@vger.kernel.org \
    /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.