From: "Ahmed Kamal" <email.ahmedkamal@googlemail.com>
To: "Tomasz Torcz" <tomek@crocom.com.pl>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: single disk reed solomon codes
Date: Mon, 21 Jul 2008 10:40:06 +0300 [thread overview]
Message-ID: <3da3b5b40807210040s72fdf458g44a1fe968088586e@mail.gmail.com> (raw)
In-Reply-To: <1216622923.6970.19.camel@s1.crocom.com.pl>
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
On Mon, Jul 21, 2008 at 9:48 AM, Tomasz Torcz <tomek@crocom.com.pl> wrote:
> Dnia 2008-07-19, sob o godzinie 17:18 +0200, Gerald Nowitzky pisze:
>
>> In the end, you would add very little security by the price of -at least-
>> cutting half your write performance. Thus, I don't think there is any point
>> in adding redundancy to single disk systems.
>
> ZFS can store multiple copies of data block within one disk. Using
> your words, it's like "Intra-Disk-RAID1". After reading data, when
> checksum shows it's corrupted, another copy (hopefully correct) is read
> from other disk location.
> This is adding security by the price of half storage capacity. Which
> seems like a fair game, given todays 1,5TB HDDs.
>
> --
> Tomasz Torcz
>
> --
> 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
>
next prev parent reply other threads:[~2008-07-21 7:40 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 [this message]
2008-07-21 13:03 ` Chris Mason
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=3da3b5b40807210040s72fdf458g44a1fe968088586e@mail.gmail.com \
--to=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