From: Roman Mamedov <rm@romanrm.ru>
To: kreijack@inwind.it
Cc: kreijack@libero.it, "Sébastien Maury" <sebastien.maury@inserm.fr>,
linux-btrfs@vger.kernel.org, "Hugo Mills" <hugo@carfax.org.uk>
Subject: Re: [RFC] btrfs fi df output [Was Re: BTRF - Storage Usage]
Date: Fri, 28 Sep 2012 09:17:59 +0600 [thread overview]
Message-ID: <20120928091759.6d096016@natsu> (raw)
In-Reply-To: <5064BEEB.1090707@libero.it>
[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]
On Thu, 27 Sep 2012 23:02:35 +0200
Goffredo Baroncelli <kreijack@libero.it> wrote:
> Sorry for the space error:
> Below a more correct example
>
> $ btrfs filesystem disk-free /
> Summary:
> Total: 135.00GB
> Allocated: 10.51GB
> Unallocated: 124.49GB
> Free_(Estimated) 86.56GB
> Average_disk_efficiency: 62 %
How do you estimate "Free" here? Sorry I didn't check the source code in git,
but from the "Details" below nothing leads me to believe that this FS is
doomed to only be able to usefully utilize only ~86GB of the partition, and not
more.
Are you ready to answer the flood of questions from people why their disk is
only 62% efficient, and how to tune it to 100%? :-)
Why use underscores instead of spaces?
>
> Details:
> Chunk-type Mode Allocated Used Free
> ---------- ---- --------- -------- ---------
> Data Single 4.01GB 2.16GB 1.87GB
> System DUP 16.00MB 4.00KB 7.99MB
> System Single 4.00MB 0.00 4.00MB
> Metadata DUP 6.00GB 429.16MB 2.57GB
> Metadata Single 8.00MB 0.00 8.00MB
--
With respect,
Roman
~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Stallman had a printer,
with code he could not see.
So he began to tinker,
and set the software free."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-09-28 3:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 10:44 BTRF - Storage Usage Sébastien Maury
2012-09-27 11:09 ` Hugo Mills
2012-09-27 11:25 ` Sébastien Maury
2012-09-27 11:43 ` Hugo Mills
2012-09-27 11:52 ` Sébastien Maury
2012-09-27 20:39 ` [RFC] btrfs fi df output [Was Re: BTRF - Storage Usage] Goffredo Baroncelli
2012-09-27 21:02 ` Goffredo Baroncelli
2012-09-28 3:17 ` Roman Mamedov [this message]
2012-09-28 8:58 ` Hugo Mills
2012-09-28 17:27 ` Goffredo Baroncelli
2012-09-28 20:13 ` Hugo Mills
2012-09-28 21:26 ` Goffredo Baroncelli
2012-09-29 7:19 ` Goffredo Baroncelli
2012-09-29 9:59 ` Sébastien Maury
2012-09-29 11:51 ` Goffredo Baroncelli
2012-11-12 18:16 ` Jan Engelhardt
2012-09-28 16:44 ` Goffredo Baroncelli
2012-09-28 18:02 ` Roman Mamedov
2012-09-28 19:38 ` Goffredo Baroncelli
2012-09-28 20:20 ` Hugo Mills
2012-09-28 21:26 ` Wade Cline
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=20120928091759.6d096016@natsu \
--to=rm@romanrm.ru \
--cc=hugo@carfax.org.uk \
--cc=kreijack@inwind.it \
--cc=kreijack@libero.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=sebastien.maury@inserm.fr \
/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).