From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs vs data deduplication
Date: Mon, 19 Sep 2011 08:14:02 +1000 [thread overview]
Message-ID: <1316384042.2249.2.camel@Nokia-N900> (raw)
In-Reply-To: <201109182215.58477.hubert@kario.pl>
On Mon, 19 Sep 2011, 06:15:51 EST, Hubert Kario <hubert@kario.pl> wrote:
> You shouldn't depend on single drive, metadata
> raid is there to protect against single bad
> blocks, not disk crash.
I guess the issue here is you no longer even
have that protection with this sort of dedup.
cheers,
Chris
--
Chris Samuel - http://www.csamuel.org/
next prev parent reply other threads:[~2011-09-18 22:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-09 6:19 btrfs vs data deduplication Paweł Brodacki
2011-09-18 20:15 ` Hubert Kario
2011-09-18 22:14 ` Chris Samuel [this message]
2011-09-18 21:01 ` Maciej Marcin Piechotka
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=1316384042.2249.2.camel@Nokia-N900 \
--to=chris@csamuel.org \
--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).