linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Szőts Ákos" <szotsaki@gmail.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: All free space eaten during defragmenting (3.14)
Date: Sat, 31 May 2014 09:19:03 +0200	[thread overview]
Message-ID: <1703083.hLnNuPsKpY@linux-suse.hu> (raw)

Dear list,

A tried to make a full defragmenting on my $HOME directory (which doesn't 
contain any snapshots). After some hours of running, it stopped with „No space 
left on device” error.

I checked and it ate about 50 GB of free space.
Before: Data, single: total=433.83GiB, used=~380.00GiB
After: Data, single: total=433.83GiB, used=~430.00GiB
Both times: Metadata, DUP: total=8.00GiB, used=7.08GiB

In the "btrfs fi df" man page I didn't find anything that is related to this 
phenomenon.

My questions are:
- Is it a bug or some consequence of the defrag process?
- Can I reclaim somehow the free space?

Command used: 
shopt -s dotglob
for i in *; do echo "$i"; btrfs fi defrag -clzo -r "$i"; done

Btrfs and kernel version:
Btrfs v3.12+20131125
Linux 3.14.4-1.gbebeb6f-desktop #1 SMP PREEMPT x86_64

Best regards,
Ákos

             reply	other threads:[~2014-05-31  7:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-31  7:19 Szőts Ákos [this message]
2014-06-01  0:56 ` All free space eaten during defragmenting (3.14) Duncan
2014-06-01  1:56   ` Duncan
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=1703083.hLnNuPsKpY@linux-suse.hu \
    --to=szotsaki@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).