public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: waxhead <waxhead@dirtcellar.net>
Cc: DanglingPointer <danglingpointerexception@gmail.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: btrfs-dedupe broken and unsupported but in official wiki
Date: Fri, 19 Jun 2020 15:19:29 +0200	[thread overview]
Message-ID: <20200619131929.GE27795@twin.jikos.cz> (raw)
In-Reply-To: <878f01ec-eb07-e8ba-bd32-143997bce422@dirtcellar.net>

On Thu, Jun 18, 2020 at 10:59:10PM +0200, waxhead wrote:
> I have pointed this out before , but I would like to use the opportunity 
> again. I, as just a regular user of btrfs would feel more comfortable if 
> the dedupe tool was part of btrfs such as for example btrfs filesystem 
> dedupe -r /somewhere

I agree that something like that would be highly useful, and despite I
know about duperemove I don't use it often enough to remember how
exactly to use it for the simple usecase.

      reply	other threads:[~2020-06-19 13:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18  2:28 btrfs-dedupe broken and unsupported but in official wiki DanglingPointer
2020-06-18 10:31 ` David Sterba
2020-06-18 20:43 ` Zygo Blaxell
2020-06-18 22:05   ` DanglingPointer
2020-06-19  5:04     ` Zygo Blaxell
2020-06-19 13:11       ` David Sterba
2020-06-22 19:49         ` Goffredo Baroncelli
2020-06-22 22:45           ` Zygo Blaxell
2020-07-02  8:27             ` Lakshmipathi.G
2020-07-03  3:16               ` Zygo Blaxell
2020-07-06 10:46                 ` Lakshmipathi.G
2020-07-25  7:24                   ` Lakshmipathi.G
2020-06-18 20:59 ` waxhead
2020-06-19 13:19   ` 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=20200619131929.GE27795@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=danglingpointerexception@gmail.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