From: Hugo Mills <hugo@carfax.org.uk>
To: Wes <anomaly256@gmail.com>
Cc: linux-btrfs@vger.kernel.org, Chester <somethingsome2000@gmail.com>
Subject: Re: btrfs filesystem df command oddly named?
Date: Fri, 27 Jan 2012 07:03:01 +0000 [thread overview]
Message-ID: <20120127070301.GD5531@carfax.org.uk> (raw)
In-Reply-To: <CAHH42iuWHH-ezUdLSzHpcqr9G69a1NdY_m4GGOmjn2jxoQwxdQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
On Fri, Jan 27, 2012 at 01:06:38PM +1100, Wes wrote:
> > I don't know much of what goes on inside BtrFS, but I like to point
> > out that btrfs fi df doesn't actually report total space on the disk,
> > only the total space currently allocated.
>
>
> Good point, and this also supports the notion that it's more of a 'du'
> work-alike than a 'df' one
On the other hand, "df" reports global figures, whereas "du"
reports values for a file or set of files. "btrfs fi df" also reports
(one set of) global figures, and a hypothetical "btrfs fi du" (which
will probably surface once Arne finishes the qgroups stuff) will
report on subvolumes and/or sets of files.
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- UNIX: British manufacturer of modular shelving units. ---
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
prev parent reply other threads:[~2012-01-27 7:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 1:11 btrfs filesystem df command oddly named? Wes
2012-01-27 1:52 ` Chester
2012-01-27 2:06 ` Wes
2012-01-27 7:03 ` Hugo Mills [this message]
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=20120127070301.GD5531@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=anomaly256@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=somethingsome2000@gmail.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).