From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: announcement of deduplication in Sun ZFS
Date: Tue, 3 Nov 2009 10:04:37 +1100 [thread overview]
Message-ID: <200911031004.57592.chris@csamuel.org> (raw)
In-Reply-To: <5f8586d40911021251n75161177s1230f44c1a4b9917@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 968 bytes --]
On Tue, 3 Nov 2009 07:51:52 am Alex Dedul wrote:
> In any way thats a nice and interesting feature, thanks! :)
My concern would be that it increases the impact of a corruption of the block
that has been de-dup'd - in other words if the block that now represents the
same data in lots of files gets trashed then all those files have corrupt
data. This implies that you would want to keep around at least one other copy
of that data to be resilient in the face of corruption (checksums will let you
detect it, but not necessarily recover from it without duplicate copies).
Given that ZFS prides itself on detecting errors it would be strange if they
hadn't considered this in the implementation but I couldn't see any mention of
it.
cheers,
Chris
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
This email may come with a PGP signature as a file. Do not panic.
For more info see: http://en.wikipedia.org/wiki/OpenPGP
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 481 bytes --]
next prev parent reply other threads:[~2009-11-02 23:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 20:25 announcement of deduplication in Sun ZFS David Nicol
2009-11-02 20:51 ` Alex Dedul
2009-11-02 23:04 ` Chris Samuel [this message]
2009-11-02 23:26 ` John Dong
2009-11-02 23:26 ` Freddie Cash
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=200911031004.57592.chris@csamuel.org \
--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 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.