From: Lars Marowsky-Bree <lmb@suse.de>
To: Selim Daoud <selim.daoud@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Multipath
Date: Tue, 26 Jul 2005 19:31:00 +0200 [thread overview]
Message-ID: <20050726173100.GZ16649@marowsky-bree.de> (raw)
In-Reply-To: <d01c0b6205072608305de15a6f@mail.gmail.com>
On 2005-07-26T16:30:13, Selim Daoud <selim.daoud@gmail.com> wrote:
> I am trying to configure multipath on a Sun SE3510FC (fibre channel)
> the configuration wiht mdadm works fine and I can see or manipulat both path.
> unfortunately as soon as I mount the md device, md_multipathd process
> takes 99% of CPU and at some point, server is not accessible anymore
> it's SUSE9SP2, with qlogic 2342 HBAs
In 2.6, work has shifted to Device-Mapper multipath.
In particular if you're running SLES9 SP2, please refer to the article
on multipathing at portal.suse.com (SDB). And if you have issues which
concern your production servers, you're going to be more happy with
asking them via your support contract instead of posting to public
mailing lists where people will tell you to try a vanilla kernel instead
;-)
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business -- Charles Darwin
"Ignorance more frequently begets confidence than does knowledge"
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2005-07-26 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 15:30 Multipath Selim Daoud
2005-07-26 17:31 ` Lars Marowsky-Bree [this message]
[not found] <200503251925.j2PJPIiG010756@smtp2.corp.netapp.com>
2005-03-25 19:31 ` multipath christophe varoqui
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=20050726173100.GZ16649@marowsky-bree.de \
--to=lmb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=selim.daoud@gmail.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.