From: Goffredo Baroncelli <kreijack@inwind.it>
To: dsterba@suse.cz, Qu Wenruo <quwenruo@cn.fujitsu.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: Format change for btrfs fi df
Date: Tue, 12 Jan 2016 20:55:22 +0100 [thread overview]
Message-ID: <56955A2A.6070708@inwind.it> (raw)
In-Reply-To: <20160112142806.GL4227@twin.jikos.cz>
On 2016-01-12 15:28, David Sterba wrote:
[...]
> How about this:
>
> - keep the global reserve in the output, separate from metadata and not
> accounted
> - add new option to account the global reserve into metadata and then
> drop it from the output
Instead of dropping it, what about prefixing it with '\_' in order to show that
it is a subtype of metadata (it is not a my idea, I read this sometime ago in
this mailing list) ?
$ btrfs fi df /
Data, single: total=29.00GiB, used=21.01GiB
System, single: total=32.00MiB, used=16.00KiB
Metadata, single: total=2.00GiB, used=716.59MiB
\_GlobalReserve, single: total=240.00MiB, used=0.00B
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
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:[~2016-01-12 19:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 5:19 [PATCH] btrfs-progs: Format change for btrfs fi df Qu Wenruo
2016-01-05 2:01 ` Qu Wenruo
2016-01-11 15:51 ` David Sterba
2016-01-12 0:20 ` Duncan
2016-01-12 14:28 ` David Sterba
2016-01-12 19:55 ` Goffredo Baroncelli [this message]
2016-01-13 0:37 ` Qu Wenruo
2016-01-12 20:46 ` Henk Slager
2016-01-13 0:35 ` Qu Wenruo
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=56955A2A.6070708@inwind.it \
--to=kreijack@inwind.it \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.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 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).