All of lore.kernel.org
 help / color / mirror / Atom feed
* Changes in multipathing between 0.4.5 (SLES9) and 0.4.7 (SLES10)
@ 2009-03-26 16:06 Lupe Christoph
  2009-03-27 15:38 ` Hannes Reinecke
  0 siblings, 1 reply; 2+ messages in thread
From: Lupe Christoph @ 2009-03-26 16:06 UTC (permalink / raw)
  To: dm-devel

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.

Thanks for any help!
Luipe Christoph
-- 
| There is no substitute for bad design except worse design.                   |
| /me                                                                          |

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Changes in multipathing between 0.4.5 (SLES9) and 0.4.7 (SLES10)
  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
  0 siblings, 0 replies; 2+ messages in thread
From: Hannes Reinecke @ 2009-03-27 15:38 UTC (permalink / raw)
  To: device-mapper development

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)

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-03-27 15:38 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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.