From: Zach Brown <zach.brown@oracle.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: jim owens <jowens@hp.com>, Morey Roof <moreyroof@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: New feature Idea
Date: Thu, 14 Aug 2008 11:49:14 -0700 [thread overview]
Message-ID: <48A47E2A.6010007@oracle.com> (raw)
In-Reply-To: <1218733937.15342.378.camel@think.oraclecorp.com>
> File granularity is not well suited to dedup when files differ by only a
> few blocks, but I'd want to see some numbers on how often that happens
> before carrying around the disk format needed to do block level dedup.
I was imagining that one could easily make a flag to debug-tree which
caused it to just dump the file block checksums from the extent items,
maybe restricted to a given subvol. Pipe that through sort and uniq -c
and you have a pretty easy path to a rough histogram of checksum values.
But I sort of wonder if the point isn't to dedup systems that were
deployed on previous-generation file systems. If people knew that dedup
worked, they might be able to more easily deploy simpler systems that
didn't have to be so careful at, say, maintaining hard link farms.
I dunno, just a thought.
- z
next prev parent reply other threads:[~2008-08-14 18:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 17:57 New feature Idea Morey Roof
2008-08-13 18:45 ` Jeff Fisher
2008-08-13 18:54 ` jim owens
2008-08-13 19:00 ` Jeff Fisher
2008-08-13 19:09 ` Morey Roof
2008-08-13 19:06 ` Joe Peterson
2008-08-13 19:28 ` jim owens
2008-08-13 19:40 ` Morey Roof
2008-08-13 19:28 ` btrfs-devel
2008-08-13 19:35 ` Kevin Cantu
2008-08-13 19:45 ` Morey Roof
2008-08-14 17:12 ` Chris Mason
2008-08-14 18:06 ` Anthony Roberts
2008-08-14 18:49 ` Zach Brown [this message]
2008-08-14 19:45 ` Morey Roof
2008-08-14 19:53 ` Chris Mason
2008-08-13 20:00 ` Andi Kleen
2008-08-13 20:10 ` Morey Roof
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=48A47E2A.6010007@oracle.com \
--to=zach.brown@oracle.com \
--cc=chris.mason@oracle.com \
--cc=jowens@hp.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=moreyroof@gmail.com \
/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.