linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Noordervliet <bart@noordervliet.net>
To: Hugo Mills <hugo-lkml@carfax.org.uk>, Chris Ball <cjb@laptop.org>,
	linux-btrfs@vger.kernel.org
Subject: Re: Update to Project_ideas wiki page
Date: Wed, 17 Nov 2010 16:12:29 +0100	[thread overview]
Message-ID: <AANLkTi=YcVE44g9waRBHQPido4_xf1o5hE4zmTPqVBxN@mail.gmail.com> (raw)
In-Reply-To: <20101117143103.GA2401@selene>

On Wed, Nov 17, 2010 at 15:31, Hugo Mills <hugo-lkml@carfax.org.uk> wro=
te:
> On Tue, Nov 16, 2010 at 10:19:45PM -0500, Chris Ball wrote:
>> =3D=3D Changing RAID levels =3D=3D
>>
>> We need ioctls to change between different raid levels. =C2=A0Some o=
f these
>> are quite easy -- e.g. for RAID0 to RAID1, we just halve the availab=
le
>> bytes on the fs, then queue a rebalance.
>
> =C2=A0 I would be interested in the rebalancing ioctls, and in RAID l=
evel
> management. I'm still very much trying to learn the basics, though, s=
o
> I may go very slowly at first...
>
> =C2=A0 Hugo.

Can I suggest we combine this new RAID level management with a
modernisation of the terminology for storage redundancy, as has been
discussed previously in the "Raid1 with 3 drives" thread of March this
year? I.e. abandon the burdened raid* terminology in favour of
something that makes more sense for a filesystem.

Mostly this would involve a discussion about what terms would make
most sense, though some changes in the behaviour of btrfs redundancy
modes may be warranted if they make things more intuitive.

I could help you make these changes in your patches, or write my own
patches against yours, though I'm also completely new to kernel
development.

Best regards,

Bart
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-11-17 15:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17  3:19 Update to Project_ideas wiki page Chris Ball
2010-11-17 14:31 ` Hugo Mills
2010-11-17 15:12   ` Bart Noordervliet [this message]
2010-11-17 17:19     ` Xavier Nicollet
2010-11-17 17:52     ` Mike Fedyk
2010-11-17 17:56     ` Hugo Mills
2010-11-17 18:07       ` Gordan Bobic
2010-11-17 18:41         ` Bart Kus
2010-11-18  8:36           ` Gordan Bobic
2010-11-18 14:31         ` Bart Noordervliet
2010-11-18 15:02           ` Justin Ossevoort
2010-11-18 15:06           ` Gordan Bobic
2010-11-17 18:14       ` Andreas Philipp
2010-11-17 18:34         ` Hugo Mills
2010-11-26 14:57   ` Paul Komkoff

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='AANLkTi=YcVE44g9waRBHQPido4_xf1o5hE4zmTPqVBxN@mail.gmail.com' \
    --to=bart@noordervliet.net \
    --cc=cjb@laptop.org \
    --cc=hugo-lkml@carfax.org.uk \
    --cc=linux-btrfs@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).