From: Johannes Hirte <johannes.hirte@datenkhaos.de>
To: Peter Becker <floyd.net@gmail.com>
Cc: Hugo Mills <hugo@carfax.org.uk>,
Tomasz Chmielewski <mangoo@wpkg.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: how to understand "btrfs fi show" output? "No space left" issues
Date: Mon, 14 Nov 2016 16:37:20 +0100 [thread overview]
Message-ID: <20161114153720.GA23564@probook> (raw)
In-Reply-To: <CAEtw4r16f10PPsVw6r5t0KP-gJbSmKEYP-zt-s5De9kSBpZEqg@mail.gmail.com>
On 2016 Sep 20, Peter Becker wrote:
> Data, RAID1: total=417.12GiB, used=131.33GiB
>
> You have 417(total)-131(used) blocks wo are only partial filled.
> You should balance your file-system.
>
> At first you need some free space. You could remove some files / old
> snapshots etc. or you add a empty USB-Stick with min. 4 GB to your
> BTRFS-Pool (after balancing complete you can remove the stick from the
> pool).
He has plenty of space. What you're describing is the case that either
data pool or metadata pool is full, the other has enough space and
nothing is left that could be allocated to the full pool. In this case
rebalancing would help. But in Tomasz' case there is enough space in
every pool, so the allocator should use it. This really sounds like a
bug.
> But at first you should try to free emty data and meta data blocks:
>
> btrfs balance start -musage=0 /mnt
> btrfs balance start -dusage=0 /mnt
Since kernel 3.18 this is done automatically.
regards,
Johannes
next prev parent reply other threads:[~2016-11-14 15:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 6:47 how to understand "btrfs fi show" output? "No space left" issues Tomasz Chmielewski
2016-09-20 6:58 ` Hugo Mills
2016-09-20 7:26 ` Tomasz Chmielewski
2016-09-20 7:27 ` Peter Becker
2016-09-20 7:28 ` Peter Becker
2016-09-20 7:30 ` Peter Becker
2016-09-20 7:51 ` Tomasz Chmielewski
2016-09-20 7:56 ` Tomasz Chmielewski
2016-09-20 8:20 ` Peter Becker
2016-09-20 8:30 ` Andrei Borzenkov
2016-09-20 8:54 ` Peter Becker
2016-09-20 8:34 ` Peter Becker
2016-09-20 8:48 ` Hugo Mills
2016-09-20 8:59 ` Peter Becker
2016-09-20 9:10 ` Peter Becker
2016-11-14 15:37 ` Johannes Hirte [this message]
2016-09-21 2:51 ` Chris Murphy
2016-09-27 3:10 ` Tomasz Chmielewski
2016-11-13 13:47 ` Tomasz Chmielewski
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=20161114153720.GA23564@probook \
--to=johannes.hirte@datenkhaos.de \
--cc=floyd.net@gmail.com \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=mangoo@wpkg.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).