From: Goffredo Baroncelli <kreijack@gmail.com>
To: linux-btrfs@vger.kernel.org, "Hugo Mills" <hugo@carfax.org.uk>,
"Roman Mamedov" <rm@romanrm.ru>,
"Sébastien Maury" <sebastien.maury@inserm.fr>,
"Ilya Dryomov" <idryomov@gmail.com>
Subject: Re: [PATCH][BTRFS-PROGS][V2] btrfs filesystem df
Date: Wed, 03 Oct 2012 21:38:29 +0200 [thread overview]
Message-ID: <506C9435.2030505@gmail.com> (raw)
In-Reply-To: <20121003193211.GX14582@twin.jikos.cz>
On 10/03/2012 09:32 PM, David Sterba wrote:
> On Wed, Oct 03, 2012 at 07:22:30PM +0200, Goffredo Baroncelli wrote:
>> $ ./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 Chunk_size Logical_size 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
>
> Please snip the following help text from basic output, eg. when I'm
> running the 'df' command before/after some actions from scripts, this
> is unnecessary.
Hi David,
the output of the program ends with the "Metadata Single....". What you
called "Help text" is a short description in the email.
BR
Goffredo
>
>> 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
>> Chunk_size -> area of disk(s) occuped by the
>> chunk (see it as raw space used)
>> Logical_size -> logical area size of the chunk
>> Used -> portion of the logical area
>> used by the filesystem
>
>
> david
>
next prev parent reply other threads:[~2012-10-03 19:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 17:22 [PATCH][BTRFS-PROGS][V2] btrfs filesystem df Goffredo Baroncelli
2012-10-03 17:22 ` [PATCH 1/2] Update btrfs filesystem df command Goffredo Baroncelli
2012-10-03 20:34 ` Ilya Dryomov
2012-10-03 20:38 ` Hugo Mills
2012-10-03 20:43 ` Ilya Dryomov
2012-10-03 20:53 ` Goffredo Baroncelli
2012-10-03 17:22 ` [PATCH 2/2] Update help page Goffredo Baroncelli
2012-10-03 19:32 ` [PATCH][BTRFS-PROGS][V2] btrfs filesystem df David Sterba
2012-10-03 19:38 ` Goffredo Baroncelli [this message]
2012-10-04 7:15 ` 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=506C9435.2030505@gmail.com \
--to=kreijack@gmail.com \
--cc=hugo@carfax.org.uk \
--cc=idryomov@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 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.