From: Neil Brown <neilb@suse.de>
To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Maybe crazy idea for reshaping: Instant/On-Demand reshaping
Date: Sun, 21 Feb 2010 13:21:27 +1100 [thread overview]
Message-ID: <20100221132127.6e49afd3@notabene.brown> (raw)
In-Reply-To: <87mxz46vj2.fsf@frosties.localdomain>
On Sat, 20 Feb 2010 11:39:29 +0100
Goswin von Brederlow <goswin-v-b@web.de> wrote:
> Neil Brown <neilb@suse.de> writes:
>
> > On Sat, 20 Feb 2010 06:27:54 +0100
> > Goswin von Brederlow <goswin-v-b@web.de> wrote:
> >> So what do you think? Is this lack of cafein speaking?
> >
> > I think your cost-benefit trade-off is way off balance on the cost side.
> >
> > This sort of complexity really belongs in a filesystem, not in a a block
> > device.
> >
> > NeilBrown
>
> So you are saying I should be using zfs instead of ext3+raid5. :)
No, I'm saying that you should fund me for a year or two so I can stop
worrying about bug fixing and md features, and can finish writing the
filesystem that I have been working on for over a decade. It will,
naturally, be able to to everything including cure the common cold.
NeilBrown
>
> When I read up on zfs last year it could not do any reshaping at
> all. You could only add new pools but not reshape an existing one.
>
> MfG
> Goswin
> --
> 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:[~2010-02-21 2:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-20 5:27 Maybe crazy idea for reshaping: Instant/On-Demand reshaping Goswin von Brederlow
2010-02-20 8:40 ` Neil Brown
2010-02-20 10:39 ` Goswin von Brederlow
2010-02-21 2:21 ` Neil Brown [this message]
2010-02-21 11:14 ` Goswin von Brederlow
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=20100221132127.6e49afd3@notabene.brown \
--to=neilb@suse.de \
--cc=goswin-v-b@web.de \
--cc=linux-raid@vger.kernel.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).