From: Neil Brown <neilb@suse.de>
To: martin f krafft <madduck@debian.org>
Cc: Christoph Hellwig <hch@lst.de>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Future of md multipath
Date: Fri, 6 Mar 2009 16:32:09 +1100 [thread overview]
Message-ID: <18864.46425.242906.213929@notabene.brown> (raw)
In-Reply-To: message from martin f krafft on Thursday March 5
On Thursday March 5, madduck@debian.org wrote:
> also sprach Neil Brown <neilb@suse.de> [2009.03.05.0349 +0100]:
> > I'm in favour of deprecating it. Whenever I hear of people using it I
> > suggest dm-multipath, but there could people I don't here about.
> > I think the upcoming mdadm-3.0 will need a compile-time option to
> > enable multipath, so people will only get it if they really really
> > want it.
>
> How do you propose a distro to deal with this? Keep it enabled for
> a certain time (with a deprecation warning?) and then just to close
> the doors on users who still need it?
>
> How long will you support it after deprecation?
>
> I understand that dm-multipath is more favourable, but unless
> there's a riskless way to convert mdadm multipath into dm-multipath
> on old systems, I don't think we have the option of deprecating it,
> unless deprecation lasts for several years.
Always the practical one, aren't you :-)
I wonder how hard it would be to get mdadm to assemble a multipath
using the 'dm' code rather than the 'md' code....
Or to get the md layer in the kernel to hook in to the dm multipath
implementation.
I think it is probably worth putting in a printk now to say "You
should probably be using dm-multipath". But we probably do need to
leave the code there for a while longer..
NeilBrown
next prev parent reply other threads:[~2009-03-06 5:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 18:04 Future of md multipath Christoph Hellwig
2009-03-05 2:49 ` Neil Brown
2009-03-05 13:00 ` martin f krafft
2009-03-06 5:32 ` Neil Brown [this message]
2009-03-06 15:17 ` martin f krafft
[not found] <cbHe8-JR-9@gated-at.bofh.it>
[not found] ` <ccbYG-sd-9@gated-at.bofh.it>
[not found] ` <ccluS-7IV-3@gated-at.bofh.it>
2009-03-07 20:08 ` Bodo Eggert
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=18864.46425.242906.213929@notabene.brown \
--to=neilb@suse.de \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=madduck@debian.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 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).