From: Goffredo Baroncelli <kreijack@libero.it>
To: Kostia Khlebopros <kkhlebopros@netgear.com>,
Sandy McArthur <sandymac@gmail.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Cc: Josef Bacik <jbacik@fb.com>
Subject: Re: What to do about df and btrfs fi df
Date: Wed, 12 Feb 2014 22:12:03 +0100 [thread overview]
Message-ID: <52FBE3A3.6040205@libero.it> (raw)
In-Reply-To: <C4D5B07324A04D4784C9F6D0FB2B0C336FFA9CA2@PERSES.netgear.com>
Hi Kostia,
On 02/12/2014 04:09 AM, Kostia Khlebopros wrote:
> Any plans on having "brtfs fi df" report more precise values rather
> then rounded off to the nearest hundredth of a unit. full
> kilobytes(1024 bytes =1Kib) or in bytes would be nice>
> Current output:
>
> # btrfs fi df /data
> Data, single: total=1.37TiB, used=1.35TiB
> System, DUP: total=8.00MiB, used=192.00KiB
> System, single: total=4.00MiB, used=0.00
> Metadata, DUP: total=3.00GiB, used=1.62GiB
> Metadata, single: total=8.00MiB, used=0.00
>
> Better would be:
>
> # btrfs fi df /data
> Data, single: total=14123412341 bytes, used=1342343 bytes
> ...etc you know what I mean...
>
My patches have a switch '-b' which set the units in byte.
$ sudo ./btrfs fi df /
Disk size: 138.05GiB
Disk allocated: 25.04GiB
Disk unallocated: 113.01GiB
Used: 21.36GiB
Free (Estimated): 105.61GiB (Max: 114.68GiB, min: 58.17GiB)
Data to disk ratio: 92 %
$ sudo ./btrfs fi df -b /
Disk size: 148229656576
Disk allocated: 26881294336
Disk unallocated: 121348362240
Used: 22939594752
Free (Estimated): 113402084997 (Max: 123134189568, min: 62460008448)
Data to disk ratio: 92 %
> I wish there was more you know.
>
> Kind Regards,
>
> Kostia
BR
G.Baroncelli
--
gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2014-02-12 21:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 16:41 What to do about df and btrfs fi df Josef Bacik
2014-02-10 17:06 ` Hugo Mills
2014-02-10 18:24 ` cwillu
2014-02-10 18:28 ` Josef Bacik
2014-02-10 18:36 ` cwillu
2014-02-10 18:41 ` Josef Bacik
2014-02-10 18:54 ` cwillu
2014-02-10 19:05 ` Hugo Mills
2014-02-11 17:36 ` David Sterba
2014-02-17 17:08 ` David Sterba
2014-02-18 8:33 ` Goswin von Brederlow
2014-02-18 16:43 ` David Sterba
2014-02-11 1:02 ` Roger Binns
2014-02-11 3:13 ` cwillu
2014-02-11 3:35 ` ronnie sahlberg
2014-02-11 19:58 ` Roger Binns
2014-02-10 22:14 ` Goffredo Baroncelli
2014-02-10 22:26 ` Goffredo Baroncelli
2014-02-10 22:56 ` cwillu
2014-02-11 13:14 ` Josef Bacik
2014-02-11 18:20 ` Goffredo Baroncelli
2014-02-11 18:33 ` Josef Bacik
2014-02-11 18:46 ` Goffredo Baroncelli
2014-02-11 18:56 ` Hugo Mills
2014-02-12 21:03 ` Goffredo Baroncelli
2014-02-11 20:53 ` Sandy McArthur
2014-02-12 3:09 ` Kostia Khlebopros
2014-02-12 21:12 ` Goffredo Baroncelli [this message]
2014-02-12 3:55 ` Anand Jain
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=52FBE3A3.6040205@libero.it \
--to=kreijack@libero.it \
--cc=jbacik@fb.com \
--cc=kkhlebopros@netgear.com \
--cc=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=sandymac@gmail.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.