From: Hugo Mills <hugo@carfax.org.uk>
To: Remi Gauvin <remi@georgianit.com>
Cc: Ulli Horlacher <framstag@rus.uni-stuttgart.de>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Understanding "btrfs filesystem usage"
Date: Mon, 29 Oct 2018 22:45:58 +0000 [thread overview]
Message-ID: <20181029224558.GE21649@carfax.org.uk> (raw)
In-Reply-To: <85a63523-7e77-f4ca-9947-2c957c5c577a@georgianit.com>
[-- Attachment #1: Type: text/plain, Size: 2312 bytes --]
On Mon, Oct 29, 2018 at 05:57:10PM -0400, Remi Gauvin wrote:
> On 2018-10-29 02:11 PM, Ulli Horlacher wrote:
> > I want to know how many free space is left and have problems in
> > interpreting the output of:
> >
> > btrfs filesystem usage
> > btrfs filesystem df
> > btrfs filesystem show
> >
> >
>
> In my not so humble opinion, the filesystem usage command has the
> easiest to understand output. It' lays out all the pertinent information.
Opinions are divided. I find it almost impossible to read, and
always use btrfs fi df and btrfs fi show together.
There's short tutorials of how to read the output in both cases in
the FAQ, which is where I start out by directing people in this
instance.
Hugo.
> You can clearly see 825GiB is allocated, with 494GiB used, therefore,
> filesystem show is actually using the "Allocated" value as "Used".
> Allocated can be thought of "Reserved For". As the output of the Usage
> command and df command clearly show, you have almost 400GiB space available.
>
> Note that the btrfs commands are clearly and explicitly displaying
> values in Binary units, (Mi, and Gi prefix, respectively). If you want
> df command to match, use -h instead of -H (see man df)
>
> An observation:
>
> The disparity between 498GiB used and 823Gib is pretty high. This is
> probably the result of using an SSD with an older kernel. If your
> kernel is not very recent, (sorry, I forget where this was fixed,
> somewhere around 4.14 or 4.15), then consider mounting with the nossd
> option. You can improve this by running a balance.
>
> Something like:
> btrfs balance start -dusage=55
>
> You do *not* want to end up with all your space allocated to Data, but
> not actually used by data. Bad things can happen if you run out of
> Unallocated space for more metadata. (not catastrophic, but awkward and
> unexpected downtime that can be a little tricky to sort out.)
>
>
> begin:vcard
> fn:Remi Gauvin
> n:Gauvin;Remi
> org:Georgian Infotech
> adr:;;3-51 Sykes St. N.;Meaford;ON;N4L 1X3;Canada
> email;internet:remi@georgianit.com
> tel;work:226-256-1545
> version:2.1
> end:vcard
>
--
Hugo Mills | Great oxymorons of the world, no. 8:
hugo@... carfax.org.uk | The Latest In Proven Technology
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2018-10-29 22:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 18:11 Understanding "btrfs filesystem usage" Ulli Horlacher
2018-10-29 21:57 ` Remi Gauvin
2018-10-29 22:45 ` Hugo Mills [this message]
2018-10-30 13:24 ` Eli V
2018-10-30 16:10 ` Ulli Horlacher
2018-10-30 17:12 ` Austin S. Hemmelgarn
2018-10-30 17:46 ` Chris Murphy
2018-10-31 12:07 ` Ulli Horlacher
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=20181029224558.GE21649@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=framstag@rus.uni-stuttgart.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=remi@georgianit.com \
/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