From: Chris Mason <chris.mason@oracle.com>
To: Ahmed Kamal <email.ahmedkamal@googlemail.com>
Cc: Tomasz Torcz <tomek@crocom.com.pl>, linux-btrfs@vger.kernel.org
Subject: Re: single disk reed solomon codes
Date: Mon, 21 Jul 2008 09:03:36 -0400 [thread overview]
Message-ID: <1216645416.6932.98.camel@think.oraclecorp.com> (raw)
In-Reply-To: <3da3b5b40807210040s72fdf458g44a1fe968088586e@mail.gmail.com>
On Mon, 2008-07-21 at 10:40 +0300, Ahmed Kamal wrote:
> I definitely hope btrfs has this per-object "copies" property too.
> However, simply replicating the whole contents of a directory, wastes
> too much disk space, as opposed to RS codes
>
Btrfs already has a raid level where things are duplicated on the single
spindles and it is on by default for metadata. mkfs isn't currently
setup to use this on data blocks, but it is certainly possible (look for
BTRFS_BLOCK_GROUP_DUP). This is definitely less reliable than two
physical devices, and I worry that such a feature would give people the
impression that single drive raid is a good idea.
As others have already said, the drives to have considerable error
detection and correction already. One of the main benefits of the
checksums is being able to tell which copy of the data from a group of
drives is correct.
In terms of detecting errors, the data checksums will do that.
-chris
next prev parent reply other threads:[~2008-07-21 13:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 12:21 single disk reed solomon codes Ahmed Kamal
2008-07-19 15:18 ` Gerald Nowitzky
2008-07-19 22:15 ` Joe Peterson
2008-07-20 1:21 ` Bron Gondwana
2008-07-21 6:48 ` Tomasz Torcz
2008-07-21 7:40 ` Ahmed Kamal
2008-07-21 13:03 ` Chris Mason [this message]
2008-07-21 15:03 ` Dongjun Shin
2008-08-04 6:52 ` Ahmed Kamal
2008-08-04 11:31 ` Ric Wheeler
2008-07-19 16:50 ` David Woodhouse
2008-07-19 16:53 ` Ahmed Kamal
2008-07-21 13:05 ` Chris Mason
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=1216645416.6932.98.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=email.ahmedkamal@googlemail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=tomek@crocom.com.pl \
/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