linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Fasheh <mfasheh@suse.de>
To: dsterba@suse.cz, Gabriel de Perthuis <g2p.code@gmail.com>,
	Josef Bacik <jbacik@fusionio.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PROGS PATCH] Import btrfs-extent-same
Date: Tue, 13 Aug 2013 12:35:15 -0700	[thread overview]
Message-ID: <20130813193515.GG31381@wotan.suse.de> (raw)
In-Reply-To: <20130806153112.GL5284@twin.jikos.cz>

Hey Dave,

On Tue, Aug 06, 2013 at 05:31:12PM +0200, David Sterba wrote:
> On Thu, Jun 27, 2013 at 12:38:19AM +0200, Gabriel de Perthuis wrote:
> > Originally from
> > https://github.com/markfasheh/duperemove/blob/master/btrfs-extent-same.c
> 
> Can you (or Mark) please turn it into a subcommand of dedup? The idea is
> to merge both in-bound and out-bound dedup into one command, eg.
> 
>  btrfs dedup files dir/*

I can handle this - it's pretty easy but we have to talk about what we're
expecting here.

Specifically, the btrfs-extent-same.c software is just a wrapper around the
ioctl. It never does actual reads of the files or data comparisons, etc. The
syntax you describe above seems like it wants an actual "scan these files
and dedupe them" which is a whole other ball game.

So I would suggest maybe something like the syhntax of btrfs-extent-same.c:

btrfs dedupe files len file1 loff1 file2 loff2 ...

Sound reasonable?
	--Mark

--
Mark Fasheh

  reply	other threads:[~2013-08-13 19:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-26 22:38 [PROGS PATCH] Import btrfs-extent-same Gabriel de Perthuis
2013-08-06 15:31 ` David Sterba
2013-08-13 19:35   ` Mark Fasheh [this message]
2013-09-02 16:43     ` David Sterba
     [not found]       ` <2014964.FiAiDKtOtq@f17simon>
2013-09-03 13:28         ` David Sterba
2013-09-03 13:41       ` David Sterba
2013-09-03 17:18         ` Mark Fasheh

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=20130813193515.GG31381@wotan.suse.de \
    --to=mfasheh@suse.de \
    --cc=dsterba@suse.cz \
    --cc=g2p.code@gmail.com \
    --cc=jbacik@fusionio.com \
    --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).