From: David Hampton <mailinglists@love2code.net>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Missing half of available space (resend)
Date: Wed, 09 Dec 2015 01:30:09 -0500 [thread overview]
Message-ID: <1449642609.20669.7.camel@love2code.net> (raw)
In-Reply-To: <CAJCQCtQrfRxrvmGT2ZA4WM6YLN5oy-+_k+NmDpv475SAtCoVNw@mail.gmail.com>
On Tue, 2015-12-08 at 22:27 -0700, Chris Murphy wrote:
> On Tue, Dec 8, 2015 at 10:02 PM, David Hampton
> <mailinglists@love2code.net> wrote:
> > The
> > 'btrfs fi df' command consistently shows a total size of around
> > 3TB, and says that space is almost completely full.
>
> and
>
>
> > root@selene:~# btrfs fi df /video
> > Data, RAID6: total=3.15TiB, used=3.11TiB
>
> The "total=3.15TiB" means "there's a total of 3.15TiB allocated for
> data chunks using raid6 profile" and of that 3.11TiB is used.
>
> btrfs fi df doesn't ever show how much is free or available.
I think I get it. The numbers in the 'df' command don't show the total
number of chunks that exist, only the subset of those chunks that have
been allocated to something.
> You can get an estimate of that by using 'btrfs fi usage' instead.
Seems I need to upgrade my tools. That command was added in 3.18 and I
only have the 3.12 tools.
> > root@selene:~# df -h /video
> > Filesystem Size Used Avail Use% Mounted on
> > /dev/vda 15T 3.2T 8.3T 28% /video
>
> That's about right although it seems it's slightly overestimating the
> available free space.
Thanks. Make me feel a lot better.
David
next prev parent reply other threads:[~2015-12-09 6:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 5:02 Missing half of available space (resend) David Hampton
2015-12-09 5:27 ` Chris Murphy
2015-12-09 6:30 ` David Hampton [this message]
2015-12-09 16:48 ` Duncan
2015-12-09 17:28 ` David Hampton
2015-12-09 19:39 ` Chris Murphy
2015-12-09 19:56 ` Gareth Pye
2015-12-09 21:26 ` David Hampton
2015-12-09 21:28 ` Chris Murphy
2015-12-09 21:41 ` David Hampton
2015-12-09 21:59 ` Gareth Pye
2015-12-10 3:27 ` 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=1449642609.20669.7.camel@love2code.net \
--to=mailinglists@love2code.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.