From: David Sterba <dsterba@suse.cz>
To: DanglingPointer <danglingpointerexception@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs-dedupe broken and unsupported but in official wiki
Date: Thu, 18 Jun 2020 12:31:35 +0200 [thread overview]
Message-ID: <20200618103135.GU27795@twin.jikos.cz> (raw)
In-Reply-To: <16bc2efa-8e88-319f-e90e-cf8536460860@gmail.com>
On Thu, Jun 18, 2020 at 12:28:41PM +1000, DanglingPointer wrote:
> btrfs-dedupe is currently broken and no longer actively supported.
>
> It no longer builds with current rustc v1.44.0 with cargo
>
> It is in the official btrfs Deduplication wiki:
>
> https://btrfs.wiki.kernel.org/index.php/Deduplication
>
> There's no real active community and proper QA, reviewing and vetting.
>
> A poster in the issues area of the projects Github location stated that
> even if fixed, it may not function correctly due to BTRFS having evolved
> since the tool was designed created.
>
> There's just too many unknowns with this BTRFS specific dedupe tool.
That's enough reason to remove the entry from the page.
> People using your official wiki and trying to use that deduplication
> program could inadvertently destroy their data through nativity or
> accident. Especially if they start trying to fix the code.
>
> I recommend you remove it from your website or at least put large
> warnings there that it is broken (which looks ugly, I would rather only
> stuff that works were there since it isn't your project anyway but some
> 3rd party).
With the 3rd party tools it's often leading to that situation and
feedback like yours helps to keep the information up to date. I'll
remove the tools that are known to be unmainained. Thanks.
next prev parent reply other threads:[~2020-06-18 10:31 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 [this message]
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
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=20200618103135.GU27795@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=danglingpointerexception@gmail.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