From: Josef Bacik <jbacik@fb.com>
To: <kreijack@inwind.it>,
"lin >> \"linux-btrfs@vger.kernel.org\""
<linux-btrfs@vger.kernel.org>
Subject: Re: What to do about df and btrfs fi df
Date: Tue, 11 Feb 2014 08:14:51 -0500 [thread overview]
Message-ID: <52FA224B.1030805@fb.com> (raw)
In-Reply-To: <52F95222.1010403@libero.it>
On 02/10/2014 05:26 PM, Goffredo Baroncelli wrote:
> On 02/10/2014 05:41 PM, Josef Bacik wrote:
>> ===== New and improved btrfs fi df =====
>>
>> Since people using this tool are already going to be better informed
>> and since we are already given the block group flags we can go ahead
>> and do the raid multiplier in btrfs-progs and spit out the adjusted
>> numbers rather than the raw numbers we get from the ioctl. This will
>> just be a progs thing and that way we can possibly add an option to
>> not apply the multipliers and just get the raw output.
>
> In the past [1] I proposed the following approach.
>
> $ sudo btrfs filesystem df /mnt/btrfs1/
> Disk size: 400.00GB
> Disk allocated: 8.04GB
> Disk unallocated: 391.97GB
> Used: 11.29MB
> Free (Estimated): 250.45GB (Max: 396.99GB, min: 201.00GB)
> Data to disk ratio: 63 %
>
> The space was given in terms of "disk space" and in terms of
> "filesystem space". Other that there is an indication of an estimation of
> the free space, with the pessimistic and optimistic values.
>
> [1] See "[PATCH V3][BTRFS-PROGS] Enhance btrfs fi df with raid5/6 support"
> dated 03/10/2013 01:17 PM
>
The problem I had with this patch was it didn't give me a way to get the
original output. I as a developer really need to have the raw dump of
the block group info as I'm doing stuff. So I like this output, but I
still need my old output, if you fix that part up I'll review/ack it.
Thanks,
Josef
next prev parent reply other threads:[~2014-02-11 13:15 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 [this message]
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
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=52FA224B.1030805@fb.com \
--to=jbacik@fb.com \
--cc=kreijack@inwind.it \
--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;
as well as URLs for NNTP newsgroup(s).