From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: Understanding "btrfs filesystem usage"
Date: Wed, 31 Oct 2018 13:07:44 +0100 [thread overview]
Message-ID: <20181031120744.GA4990@rus.uni-stuttgart.de> (raw)
In-Reply-To: <20181030161003.GA25765@rus.uni-stuttgart.de>
On Tue 2018-10-30 (17:10), Ulli Horlacher wrote:
>
> On Mon 2018-10-29 (17:57), 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.
> >
> > 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".
>
> And what is "Device unallocated"? Not reserved?
The answer is in the FAQ and I am stupid not to looked at it, first :-}
https://btrfs.wiki.kernel.org/index.php/FAQ#How_much_free_space_do_I_have.3F
--
Ullrich Horlacher Server und Virtualisierung
Rechenzentrum TIK
Universitaet Stuttgart E-Mail: horlacher@tik.uni-stuttgart.de
Allmandring 30a Tel: ++49-711-68565868
70569 Stuttgart (Germany) WWW: http://www.tik.uni-stuttgart.de/
REF:<20181030161003.GA25765@rus.uni-stuttgart.de>
prev parent reply other threads:[~2018-10-31 12:07 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
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 [this message]
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=20181031120744.GA4990@rus.uni-stuttgart.de \
--to=framstag@rus.uni-stuttgart.de \
--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