From: David Taylor <davidt-btrfs@yadt.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 07/14] btrfs-progs: Print more info about device sizes
Date: Wed, 30 Apr 2014 14:37:16 +0100 [thread overview]
Message-ID: <20140430133715.GA7571@yadt.co.uk> (raw)
In-Reply-To: <5360FB26.9090009@kingswood-consulting.co.uk>
On Wed, 30 Apr 2014, Frank Kingswood wrote:
> On 30/04/14 13:11, David Sterba wrote:
>> On Wed, Apr 30, 2014 at 01:39:27PM +0200, Goffredo Baroncelli wrote:
>>>
>>> I found a bit unclear the "FS occupied" terms.
>>
>> We're running out of terms to describe and distinguish the space that
>> the filesystem uses.
>>
>> 'occupied' seemed like a good choice to me, though it may be not obvious
>
> The space that the filesystem uses in total seems to me is called the
> "size". It has nothing to do with utilization.
>
> /dev/sda6, ID: 2
> Device size: 10.00GiB
> Filesystem size: 5.00GiB
FS size was what I was about to suggest, before I saw your reply.
It makes more sense to me than 'Occupied' and seems cleaner than
'Resized To'. It sort of mirrors how LVM describes PV / VG / LV
sizes, too.
--
David Taylor
next prev parent reply other threads:[~2014-04-30 13:42 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 15:56 [PATCH 00/14] Enhanced df - followup David Sterba
2014-04-29 15:57 ` [PATCH 01/14] btrfs-progs: read global reserve size from space infos David Sterba
2014-04-29 15:57 ` [PATCH 02/14] btrfs-progs: add original 'df' and rename 'disk_usage' to 'usage' David Sterba
2014-04-29 15:58 ` [PATCH 03/14] btrfs-progs: move device usage to cmds-device, more cleanups David Sterba
2014-04-29 15:58 ` [PATCH 04/14] btrfs-progs: check if we can't get info from ioctls due to permissions David Sterba
2014-04-29 16:01 ` [PATCH 05/14] btrfs-progs: zero out structures before calling ioctl David Sterba
2014-04-29 16:02 ` [PATCH 06/14] btrfs-progs: print B for bytes David Sterba
2014-04-29 16:02 ` [PATCH 07/14] btrfs-progs: Print more info about device sizes David Sterba
2014-04-29 19:23 ` Mike Fleetwood
2014-04-30 11:39 ` Goffredo Baroncelli
2014-04-30 12:11 ` David Sterba
2014-04-30 13:31 ` Frank Kingswood
2014-04-30 13:37 ` David Taylor [this message]
2014-04-30 17:38 ` Goffredo Baroncelli
2014-05-02 13:13 ` David Sterba
2014-05-02 13:15 ` David Sterba
2014-05-14 18:00 ` David Sterba
2014-04-30 11:52 ` David Sterba
2014-04-29 16:02 ` [PATCH 08/14] btrfs-progs: compare unallocated space against the correct value David Sterba
2014-04-29 16:02 ` [PATCH 09/14] btrfs-progs: add section of overall filesystem usage David Sterba
2014-04-29 16:02 ` [PATCH 10/14] btrfs-progs: cleanup filesystem/device usage code David Sterba
2014-04-29 16:02 ` [PATCH 11/14] btrfs-progs: extend pretty printers with unit mode David Sterba
2014-04-29 16:02 ` [PATCH 12/14] btrfs-progs: replace df_pretty_sizes with pretty_size_mode David Sterba
2014-04-29 16:02 ` [PATCH 13/14] btrfs-progs: clean up return codes and paths David Sterba
2014-04-29 16:03 ` [PATCH 14/14] btrfs-progs: move global reserve to overall summary David Sterba
2014-04-29 17:10 ` [PATCH 00/14] Enhanced df - followup Duncan
2014-04-29 17:17 ` Marc MERLIN
2014-04-29 17:33 ` Holger Hoffstätte
2014-04-30 0:42 ` Duncan
2014-04-30 8:15 ` Martin Steigerwald
2014-04-30 12:37 ` David Sterba
2014-04-30 13:01 ` David Sterba
2014-04-30 17:25 ` Duncan
2014-04-29 19:14 ` Mike Fleetwood
2014-04-30 12:22 ` David Sterba
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=20140430133715.GA7571@yadt.co.uk \
--to=davidt-btrfs@yadt.co.uk \
--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).