From: Luca Berra <bluca@comedia.it>
To: Ionut Nistor <ionut@modulo.ro>
Cc: linux-raid@vger.kernel.org
Subject: Re: Multipath problem in a SAN enviromnent
Date: Wed, 11 Jun 2003 21:24:16 +0200 [thread overview]
Message-ID: <3EE781E0.1020707@comedia.it> (raw)
In-Reply-To: <02d201c33023$13fd45a0$3351960a@EEL>
Ionut Nistor wrote:
> Hello,
>
> I'm using a 2.4.18-ac3 kernel and the multipath module in order to ensure
> automatic IO path failover. The systems connect to a FC SAN environment.
> New logical disks are added/removed from the SAN periodically.
>
> Unfortunatelly, linux's raid subsystem uses major and minor numbers in the
> superblock in order to identify members for all raid types - including
> multipath. This causes the multipath module to fail when attempting to
> identify the members. When the scsi driver is loaded, the bus is scanned and
> all the available devices/targets/luns are added to the scsi subsystem and
> are allocated a major and minor number.
>
you mean autodetection fails? don't use autodetection.
regards,
Luca.
next prev parent reply other threads:[~2003-06-11 19:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 14:09 Multipath problem in a SAN enviromnent Ionut Nistor
2003-06-11 15:49 ` Dominik Kubla
2003-06-11 16:47 ` Ionut Nistor
2003-06-11 16:27 ` Paul Clements
2003-06-11 16:42 ` Moving Disks [Re: Multipath problem in a SAN enviromnent] Gordon Henderson
2003-06-11 16:45 ` Multipath problem in a SAN enviromnent Ionut Nistor
2003-06-11 17:59 ` Paul Clements
2003-06-12 6:28 ` Ionut Nistor
2003-06-12 10:04 ` Lars Marowsky-Bree
2003-06-12 10:51 ` Ionut Nistor
2003-06-12 14:52 ` Paul Clements
2003-06-13 8:12 ` Ionut Nistor
2003-06-18 10:21 ` Lars Marowsky-Bree
2003-06-19 15:25 ` Ionut Nistor
2003-06-11 19:24 ` Luca Berra [this message]
2003-06-12 6:35 ` Ionut Nistor
2003-06-11 19:34 ` Paul Clements
2003-06-12 6:37 ` Ionut Nistor
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=3EE781E0.1020707@comedia.it \
--to=bluca@comedia.it \
--cc=ionut@modulo.ro \
--cc=linux-raid@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.