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: Changes in multipathing between 0.4.5 (SLES9) and 0.4.7	(SLES10)
Date: Fri, 27 Mar 2009 16:38:08 +0100	[thread overview]
Message-ID: <49CCF2E0.7010009@suse.de> (raw)
In-Reply-To: <20090326160641.GA12038@lupe-christoph.de>

Hi,

Lupe Christoph wrote:
> Hi!
> 
> I just ran into a strange difference in the behavious of multipathing
> between SLES9 and SLES10. While SLES9 seemed to ignore single-pathed
> disks like volumes on the internal RAID controller of IBM xSeries,
> SLES10 welcomes them leading to different pathes in /etc/fstab.
> 
> There is a lot of our software involved in this behavious, so let's just
> say that the change is unwelcome ;-)
> 
> We have for now overcome this by blacklisting the internal RAID
> controller. But there are many types of RAID controllers involved (the
> machines have all hardware-mirrored internal disks), so we would like to
> have a better solution.
> 
> Is there a way to tell the multipath-tools to ignore devices that have
> only a single path? I found nothing in the multipath.conf manpage, but
> maybe I read it wrong.
> 
No, there isn't. For multipathing we cannot distinguish between 'real'
single path systems and multipath systems with all but one path failed.
So whenever multipath is activated we have to assume that the admin
really wants to have multipath, and consequently the admin will have
to take appropriate steps.

Although there is no harm in running the system entirely on multipath;
the performance impact for the root fs is negligible ...

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:[~2009-03-27 15:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26 16:06 Changes in multipathing between 0.4.5 (SLES9) and 0.4.7 (SLES10) Lupe Christoph
2009-03-27 15:38 ` Hannes Reinecke [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=49CCF2E0.7010009@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.