linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Svist <fry.kun@gmail.com>
To: Austin S Hemmelgarn <ahferroin7@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: bedup --defrag freezing
Date: Wed, 12 Aug 2015 11:44:59 -0700	[thread overview]
Message-ID: <55CB942B.7050301@gmail.com> (raw)
In-Reply-To: <55C340B5.20005@gmail.com>

On 08/06/2015 04:10 AM, Austin S Hemmelgarn wrote:
> On 2015-08-05 17:45, Konstantin Svist wrote:
>> Hi,
>>
>> I've been running btrfs on Fedora for a while now, with bedup --defrag
>> running in a night-time cronjob.
>> Last few runs seem to have gotten stuck, without possibility of even
>> killing the process (kill -9 doesn't work) -- all I could do is hard
>> power cycle.
>>
>> Did something change recently? Is bedup simply too out of date? What
>> should I use to de-duplicate across snapshots instead? Etc.?
>>
> AFAIK, bedup hasn't been actively developed for quite a while (I'm
> actually kind of surprised it runs with the newest btrfs-progs).
> Personally, I'd suggest using duperemove
> (https://github.com/markfasheh/duperemove)

Thanks, good to know.
Tried duperemove -- it looks like it builds a database of its own
checksums every time it runs... why won't it use BTRFS internal
checksums for fast rejection? Would run a LOT faster...



  reply	other threads:[~2015-08-12 18:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05 21:45 bedup --defrag freezing Konstantin Svist
2015-08-06 11:10 ` Austin S Hemmelgarn
2015-08-12 18:44   ` Konstantin Svist [this message]
2015-08-12 19:30     ` Chris Murphy
2015-08-13 11:30       ` Austin S Hemmelgarn

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=55CB942B.7050301@gmail.com \
    --to=fry.kun@gmail.com \
    --cc=ahferroin7@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;
as well as URLs for NNTP newsgroup(s).