From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Peter Becker <floyd.net@gmail.com>
Cc: Hugo Mills <hugo@carfax.org.uk>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: how to understand "btrfs fi show" output? "No space left" issues
Date: Tue, 20 Sep 2016 16:56:50 +0900 [thread overview]
Message-ID: <6596b749c3c4b37dc1db8c3a766be491@admin.virtall.com> (raw)
In-Reply-To: <CAEtw4r16f10PPsVw6r5t0KP-gJbSmKEYP-zt-s5De9kSBpZEqg@mail.gmail.com>
On 2016-09-20 16:27, Peter Becker wrote:
> You have 417(total)-131(used) blocks wo are only partial filled.
> You should balance your file-system.
(...)
> #or a full balance
> btrfs balance start /mnt
OK, does it mean that btrfs needs some userspace daemon which does the
following from time to time (how often?):
1) btrfs fi show /mountpoint(s)
2) if "used" is more than 90% (or 80%? or 70%?) of "size" - run a full
balance
3) ...unless "btrfs fi df" shows that "used" is 95% (?) or more of
"total", then don't bother, as we're "really" full
?
Tomasz Chmielewski
https://lxadm.com
next prev parent reply other threads:[~2016-09-20 7:56 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 [this message]
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
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=6596b749c3c4b37dc1db8c3a766be491@admin.virtall.com \
--to=mangoo@wpkg.org \
--cc=floyd.net@gmail.com \
--cc=hugo@carfax.org.uk \
--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).