linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Pharaoh <james@pharaoh.uk>
To: linux-btrfs@vger.kernel.org
Subject: Announcing btrfs-dedupe 1.1.0
Date: Sun, 8 Jan 2017 17:57:02 +0100	[thread overview]
Message-ID: <b81e1e04-394b-06a8-d4cb-acfe436a8423@pharaoh.uk> (raw)

Hi everyone,

I'm pleased to announce a new version of my btrfs-dedupe tool, written 
in rust, available here:

http://btrfs-dedupe.com/

Binary packages built on ubuntu (probably will work elsewhere, but 
haven't tried this), are available at:

https://dist.wellbehavedsoftware.com/btrfs-dedupe/

This version is considered ready for production use. It maintains a 
compressed database of the filesystem state, and it tracks file 
metadata, hashes file contents, and the extent-map contents, in order to 
work out what needs to be deduplicated.

This is a whole-file deduplication tool, similar to bedup, but since it 
is written in Rust, and designed to work with the dedupe ioctl, I think 
it's more suitable for production use.

As normal for open source, this comes without any warranty etc, but the 
only updates are performed via the defragment and deduplication ioctls, 
and so assuming they work correctly then this should not cause any 
corruption.

Please feel free to contact me with any questions/problems.

             reply	other threads:[~2017-01-08 17:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-08 16:57 James Pharaoh [this message]
     [not found] ` <a665ce04-b168-0783-baf2-d32a4679aa0a@mailb.org>
2017-01-08 22:04   ` Announcing btrfs-dedupe 1.1.0 James Pharaoh
2017-01-13 12:56 ` Robert Krig
2017-01-13 19:08   ` James Pharaoh
2017-01-26 17:16     ` Robert Krig
2017-01-26 17:44       ` James Pharaoh

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=b81e1e04-394b-06a8-d4cb-acfe436a8423@pharaoh.uk \
    --to=james@pharaoh.uk \
    --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).