From: David Sterba <dave@jikos.cz>
To: Goffredo Baroncelli <kreijack@gmail.com>
Cc: "Chris Mason" <chris.mason@fusionio.com>,
"Hugo Mills" <hugo@carfax.org.uk>,
"Roman Mamedov" <rm@romanrm.ru>,
"Sébastien Maury" <sebastien.maury@inserm.fr>,
"Ilya Dryomov" <idryomov@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH][BTRFS-PROGS][V3] btrfs filesystem df
Date: Tue, 9 Oct 2012 15:51:38 +0200 [thread overview]
Message-ID: <20121009135138.GP4405@twin.jikos.cz> (raw)
In-Reply-To: <1349371679-10775-1-git-send-email-kreijack@inwind.com>
Hi,
I hope I'm not late to the bikeshedding party, I've tried to use the
proposed version and here are my observations/wishes, and also issues,
pointed out in the threads, that were not addressed:
* I'd like to re-add the -s -d options in some way that I can choose
which sections I'll see; the previous output matches the 'details'
section and contains the valuable information for me
More flexibility via options will satisfy more users, currently I have
no choice than only ignore the summary section, not to say that this
consumes half of my terminal
UI details (that make human-parsing of the output more pleasant experience):
* the 'Path' should contain full path, not just the argument that was
given (otherwise it's useless)
* I'm with Hugo that there should be space between numbers and units
* show the byte units
* the short form for metadata in --mixed filesystem
current: Data+M.data
proposed: Data+Meta
* Chunk_type -> Type ?
* Size_(logical) is misaligned with the numbers underneath
* Used (in the summary) is in logical units, I needed to hand calculate
the number to find this out -- any idea how to make it more clear?
like Used_(logical) similar to size
* revert the order of Min and Max in Free_(Estimated)
* in code: function is still named cmd_disk_free
* in code: although you've removed -s -d the getopt string still
contains them (but this is not an objection because I want them back :)
Also, I've noticed that you refuse to fix minor things in code that
you're not touching directly for 'df', but this renders the (much
needed!) updates to df as only half-finished (IMHO). It's fine to add a
separate patch to fix up the non-df things. Let's fix it in one go :)
thanks,
david
[Sample output for quick reference]
> $ ./btrfs filesystem df /
> Path: /
> Summary:
> Disk_size: 72.57GB
> Disk_allocated: 25.10GB
> Disk_unallocated: 47.48GB
> Logical_size: 23.06GB
> Used: 11.01GB
> Free_(Estimated): 55.66GB (Max: 59.52GB, Min: 35.78GB)
> Data_to_disk_ratio: 92 %
>
> Details:
> Chunk_type Mode Size_(disk) Size_(logical) Used
> Data Single 21.01GB 21.01GB 10.34GB
> System DUP 80.00MB 40.00MB 4.00KB
> System Single 4.00MB 4.00MB 0.00
> Metadata DUP 4.00GB 2.00GB 686.93MB
> Metadata Single 8.00MB 8.00MB 0.00
>
> Where:
> Disk_size -> sum of sizes of teh disks
> Disk_allocated -> sum of chunk sizes
> Disk_unallocated -> Disk_size - Disk_allocated
> Logical_size -> sum of logical area sizes
> Used -> logical area used
> Free_(Estimated) -> on the basis of allocated
> chunk, an estrapolation of
> the free space
> Data_to_disk_ratio -> ration between the space occuped
> by a chunk and the real space
> available ( due to duplication
> and/or RAID level)
> Chunk_type -> kind of chunk
> Mode -> allocation policy of a chunk
> Size_(disk) -> area of disk(s) occuped by the
> chunk (see it as raw space used)
> Size_(logical) -> logical area size of the chunk
> Used -> portion of the logical area
> used by the filesystem
next prev parent reply other threads:[~2012-10-09 13:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 17:27 [PATCH][BTRFS-PROGS][V3] btrfs filesystem df Goffredo Baroncelli
2012-10-04 17:27 ` [PATCH 1/2] Update btrfs filesystem df command Goffredo Baroncelli
2012-10-04 17:27 ` [PATCH 2/2] Update help page Goffredo Baroncelli
2012-10-06 9:57 ` [PATCH][BTRFS-PROGS][V3] btrfs filesystem df Martin Steigerwald
2012-10-06 13:47 ` Goffredo Baroncelli
2012-10-09 13:51 ` David Sterba [this message]
2012-10-09 18:07 ` Goffredo Baroncelli
2012-10-09 22:15 ` David Sterba
2012-10-10 17:26 ` Goffredo Baroncelli
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=20121009135138.GP4405@twin.jikos.cz \
--to=dave@jikos.cz \
--cc=chris.mason@fusionio.com \
--cc=hugo@carfax.org.uk \
--cc=idryomov@gmail.com \
--cc=kreijack@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rm@romanrm.ru \
--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).