From: Chris Mason <chris.mason@oracle.com>
To: btrfs-devel@oss.oracle.com, linux-btrfs@vger.kernel.org
Subject: Re: Checksums and self-healing roadmap
Date: Tue, 1 Apr 2008 13:41:15 -0400 [thread overview]
Message-ID: <200804011341.15923.chris.mason@oracle.com> (raw)
In-Reply-To: <1205846009.8520.14.camel@s1.crocom.com.pl>
On Tuesday 18 March 2008, Tomasz Torcz wrote:
> Hi,
>
> I've read btrfs roadmap and skimmed through the code trying to learn
> about self-healing in btrfs. Sadly I found none. If I understand
> correctly, upon detecting checksum error btrfs will only report it via
> printk() (in csum_tree_block()). Self-healing is most important feature
> of ZFS for me.
Correct, we currently only report errors without taking corrective actions.
>
> As far as I understand, to have self healing in btrfs, first multiple
> devices spanning and configuration like raid1 must be implemented. Also
> multiples copies per subvolume (via btrfsctl I suppose) would be nice to
> have. Device spanning is in Roadmap. But what with other features? When
> they're planned?
Support for multiple devices exists today in the unstable trees, and it
currently includes simple device concatenation and raid0. Raid1 is in
progress, and should be done shortly. The plan is to stabilize all of this
code over the month of April and release v0.14 with it at the end of the
month.
-chris
parent reply other threads:[~2008-04-01 17:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1205846009.8520.14.camel@s1.crocom.com.pl>]
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=200804011341.15923.chris.mason@oracle.com \
--to=chris.mason@oracle.com \
--cc=btrfs-devel@oss.oracle.com \
--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).