From: Lars Marowsky-Bree <lmb@suse.de>
To: Dominik Kubla <dominik.kubla@uni-mainz.de>,
Neil Brown <neilb@cse.unsw.edu.au>
Cc: Dominik Kubla <kubla@uni-mainz.de>,
linux-raid@vger.kernel.org, khoddam@netz.klinik.uni-mainz.de
Subject: Re: Bug in multipath code (Linux 2.6.x) ?
Date: Tue, 13 Apr 2004 10:04:17 +0200 [thread overview]
Message-ID: <20040413080417.GG5271@marowsky-bree.de> (raw)
In-Reply-To: <200404101011.58547.dominik.kubla@uni-mainz.de>
On 2004-04-10T10:11:58,
Dominik Kubla <dominik.kubla@uni-mainz.de> said:
> Understandable. Maybe the Linux SAN-Alliance should sponsor you a couple of
> HBAs and a JBOD... ;-)
A lot of work has gone into the Device-Mapper multipath target in 2.6;
maybe you should look at that one.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering \ ever tried. ever failed. no matter.
SUSE Labs | try again. fail again. fail better.
Research & Development, SUSE LINUX AG \ -- Samuel Beckett
-
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:[~2004-04-13 8:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 18:33 Bug in multipath code (Linux 2.6.x) ? Dominik Kubla
2004-04-07 22:37 ` Neil Brown
2004-04-10 8:11 ` Dominik Kubla
2004-04-13 8:04 ` Lars Marowsky-Bree [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-13 10:46 Dominik Kubla
2004-04-14 11:09 ` Jure Pecar
2004-04-25 22:02 christophe varoqui
2004-04-26 13:34 ` Dominik Kubla
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=20040413080417.GG5271@marowsky-bree.de \
--to=lmb@suse.de \
--cc=dominik.kubla@uni-mainz.de \
--cc=khoddam@netz.klinik.uni-mainz.de \
--cc=kubla@uni-mainz.de \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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).