From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: All free space eaten during defragmenting (3.14)
Date: Sun, 1 Jun 2014 01:56:55 +0000 (UTC) [thread overview]
Message-ID: <pan$26939$a2addb4c$9febc316$74bf1551@cox.net> (raw)
In-Reply-To: pan$d1ec3$d22b3db$8681b9b1$d9742e40@cox.net
Duncan posted on Sun, 01 Jun 2014 00:56:09 +0000 as excerpted:
> As for reclaiming the space...
One more option there I forgot to mention... There are various dedup
tools out there. See the wiki ( https://btrfs.wiki.kernel.org ) and the
list archive for more as I've not used any of them myself, but in theory
at least, the dedup tools should help you recover the space, and I /
think/ they'll do so without forcing either snapshot deletion or a fresh
mkfs.btrfs and restore from backup, too, those being the other options I
mentioned.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-06-01 2:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-31 7:19 All free space eaten during defragmenting (3.14) Szőts Ákos
2014-06-01 0:56 ` Duncan
2014-06-01 1:56 ` Duncan [this message]
2014-06-01 20:39 ` Peter Chant
2014-06-01 22:47 ` Duncan
2014-06-02 20:54 ` Peter Chant
2014-06-03 4:46 ` Duncan
2014-06-03 22:21 ` Peter Chant
2014-06-04 9:21 ` Duncan
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='pan$26939$a2addb4c$9febc316$74bf1551@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).