Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: waxhead <waxhead@dirtcellar.net>
Cc: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: Btrfs progs release 6.1
Date: Mon, 9 Jan 2023 23:35:03 +0100	[thread overview]
Message-ID: <20230109223503.GY11562@twin.jikos.cz> (raw)
In-Reply-To: <00ac11fa-b6c9-6234-50db-3af1c2ae826c@dirtcellar.net>

On Sat, Dec 24, 2022 at 11:20:20AM +0100, waxhead wrote:
> I have nagged about this before, but here goes again.
> Can we as users get some kind of deduplicaiton support for btrfs-progs?
> 
> As a conservative Debian user I tend to stick with what is in the 
> package repos, and I also believe that most people will feel more 
> comfortable with a "official" implementation rather than some random 
> program for this kind of stuff.
> 
> something as "simple" as "btrfs filesystem deduplicate -R /mnt" would be 
> wonderful.

Yes, this is planned, it would be convenient to quickly deduplicate a
few files or let it work on a directory. This would probably copy what
duperemove does and most likely also steal the implementation as it's in
C.

I'm not sure if btrfs command should provide exactly the same set of
features and options and duplicate the project, I think dupremove is not
currently maintained. I don't want to reimplement everything from
scratch so some level of sharing will make things easier, either direct
copy or as git submodule. It'll start as an experimental command.

      reply	other threads:[~2023-01-09 22:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-22 20:57 Btrfs progs release 6.1 David Sterba
2022-12-24 10:20 ` waxhead
2023-01-09 22:35   ` David Sterba [this message]

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=20230109223503.GY11562@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=waxhead@dirtcellar.net \
    /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