linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lars Marowsky-Bree <lmb@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [dm-devel] [multipath] SCSI device capacity mess
Date: Thu, 28 Oct 2004 13:35:50 +0200	[thread overview]
Message-ID: <20041028113550.GS32712@marowsky-bree.de> (raw)
In-Reply-To: <1098903759.12464.32.camel@zezette>

On 2004-10-27T21:02:39, christophe varoqui <christophe.varoqui@free.fr> wrote:

> > As a note, this is one mode the EMC CLARiiON arrays can also operate in.
> > Even worse, they won't present the block device at all, just the SCSI
> > generic mode. However, for the CLARiiONs, they can be configured to
> > behave sanely and reply to a READ_CAPACITY too (just all I/O will be
> > errored), if setting the failovermode to 1.
> > 
> > I wonder whether your system can also be configured as such?
> Yes it could, but it's a controler wide setting.

Not per LUN? Too bad.

> Compatibility with other OS sharing the same controlers might impose
> this mode though. So I'd like to straight this situation up.

Then I think hardware-specific hooks in the dm-mpath are the way to go.
We already have them in place for the priority group initialization code
anyway, we can add them for anything else which needs them, like this
one.

> I wonder if it's not simpler just to remove the NOSTARTONADD flag on
> this devices in scsi_devinfo.c. I tested that and all the READ CAPACITY
> succeed as expected (DEC HSG80 / COMPAQ HSV*).

As James points out, this won't be quite the thing to do.


Sincerely,
    Lars Marowsky-Brée <lmb@suse.de>

-- 
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX AG - A Novell company

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2004-10-28 17:54 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
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 [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=20041028113550.GS32712@marowsky-bree.de \
    --to=lmb@suse.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).