From: Oliver Mattos <oliver.mattos08@imperial.ac.uk>
To: Ray Van Dolson <rayvd@bludgeon.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Cc: Tracy Reed <treed@tracyreed.org>,
<btrfs-devel@arbitraryconstant.com>,
Chris Mason <chris.mason@oracle.com>,
<linux-btrfs@vger.kernel.org>
Subject: Re: Data De-duplication
Date: Thu, 11 Dec 2008 00:18:11 +0000 [thread overview]
Message-ID: <1228954691.7571.33.camel@mattos-laptop> (raw)
In-Reply-To: <20081210221006.GA30484@bludgeon.org>
> It would be interesting to see how many duplicate *blocks* there are
> across the filesystem, agnostic to files...
>
> Is this somthing your script does Oliver?
My script doesn't yet exist, although when created it would, yes. I was
thinking of just making a BASH script and using dd to extract 512 byte
chunks of files, pipe through md5sum and save the result in a large
index file. Next just iterate through the index file looking for
duplicate hashes.
In fact that sounds so easy I might do it right now... (only to proof
of concept stage - a real utility would probably want to be written in a
compiled language and use proper trees for faster searching)
next prev parent reply other threads:[~2008-12-11 0:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 22:48 Data De-duplication Oliver Mattos
2008-12-10 11:52 ` Miguel Figueiredo Mascarenhas Sousa Filipe
2008-12-10 13:30 ` Chris Mason
2008-12-10 17:53 ` Oliver Mattos
2008-12-11 15:12 ` Chris Mason
[not found] ` <32809.2001:470:e828:1::2:2.1228939660.squirrel@avalon.arbitraryconstant.com>
2008-12-10 21:10 ` Oliver Mattos
2008-12-10 21:19 ` Ray Van Dolson
2008-12-10 21:42 ` Oliver Mattos
2008-12-10 21:57 ` Tracy Reed
2008-12-10 22:06 ` Oliver Mattos
2008-12-10 22:10 ` Ray Van Dolson
2008-12-11 0:18 ` Oliver Mattos [this message]
2008-12-11 3:42 ` Oliver Mattos
2008-12-11 3:50 ` Ray Van Dolson
2008-12-11 9:58 ` Oliver Mattos
2008-12-14 19:37 ` Omen Wild
2008-12-14 12:25 ` Chris Samuel
2008-12-10 13:30 ` seth huang
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=1228954691.7571.33.camel@mattos-laptop \
--to=oliver.mattos08@imperial.ac.uk \
--cc=btrfs-devel@arbitraryconstant.com \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rayvd@bludgeon.org \
--cc=treed@tracyreed.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