From: Chris Mason <chris.mason@oracle.com>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs wishlist
Date: Tue, 01 Mar 2011 13:39:58 -0500 [thread overview]
Message-ID: <1299004651-sup-1713@think> (raw)
In-Reply-To: <28499638.308.1299004542529.JavaMail.root@zimbra>
Excerpts from Roy Sigurd Karlsbakk's message of 2011-03-01 13:35:42 -0500:
> Hi all
>
> Having managed ZFS for about two years, I want to post a wishlist.
>
> INCLUDED IN ZFS
>
> - Mirror existing single-drive filesystem, as in 'zfs attach'
This one is easy, we do plan on adding it.
> - RAIDz-stuff - single and hopefully multiple-parity RAID configuration with block-level checksumming
We'll have raid56, but it won't be variable stripe size. There will be
one stripe size for data and one for metadata but that's it.
> - Background scrub/fsck
These are in the works
> - Pool-like management with multiple RAIDs/mirrors (VDEVs)
We have a pool of drives now....I'm not sure exactly what the vdevs are.
> - Autogrow as in ZFS autoexpand
We grow to the available storage now.
>
> NOT INCLUDED IN CURRENT ZFS
>
> - Adding/removing drives from VDEVs
We can add and remove drives on the fly today
> - Rebalancing a pool
We can rebalance space between drives today.
> - dedup
ZFS does have dedup we don't yet. This one has a firm maybe.
-chris
next prev parent reply other threads:[~2011-03-01 18:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 18:35 btrfs wishlist Roy Sigurd Karlsbakk
2011-03-01 18:39 ` Chris Mason [this message]
2011-03-01 19:09 ` Freddie Cash
2011-03-02 9:05 ` Thomas Bellman
2011-03-02 10:43 ` Hugo Mills
2011-03-02 14:18 ` Justin Ossevoort
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=1299004651-sup-1713@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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.