From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: linux-btrfs@vger.kernel.org
Subject: Is BTRFS "bedup" maintained ?
Date: Sun, 02 Mar 2014 12:00:51 +0100 [thread overview]
Message-ID: <2507621.pWqlrcrh1e@fnix> (raw)
Hello,
I tried to use "bedup" BTRFS offline deduplication tool on several BTRFS
machines, with mixed results :
1/ Crashes with messages stating "programming error", sqlite objects must be
used inside of the thread that created them, blah-blah...
2/ Crashes stating that some file/objects miss a "live" attribute (?)
3/ bedup eating all my system RAM, then swap over 7GB until the system trashes
itself.
Wel, besides that and restarting over and over, I could deduplicate some files
and gain some noticeable space, but it looks extremely bugged and unreliable.
I tried to email the maintainer with details, twice, thru 2 different channels,
got no anwser...
And it looks like the GIT has not evolved since August, 2013.
So my questions are :
- Is "bedup" maintained or abandoned ?
- Is it supposed to be usable ?
- Should I use it ?
- Is there a risk that it causes data loss or corruption ?
TIA.
Kind regards.
--
Swâmi Petaramesh <swami@petaramesh.org> http://petaramesh.org PGP 9076E32E
reply other threads:[~2014-03-02 10:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2507621.pWqlrcrh1e@fnix \
--to=swami@petaramesh.org \
--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