From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs and integration with GNU ++
Date: Mon, 18 May 2015 08:57:32 +0000 (UTC) [thread overview]
Message-ID: <pan$4770b$fa4970d7$3ce3a170$4499f64@cox.net> (raw)
In-Reply-To: pan$87dbc$361c1d30$d0fc2fb2$5646ab5d@cox.net
Duncan posted on Mon, 18 May 2015 06:41:09 +0000 as excerpted:
>> Currently, df seems to show good data, while du doesn't.
>
> There has been some work put into what df returns to make it so, while
> similar work to du has not yet been released, and in fact only quite
> recently (within the last month) has been proposed on the list.
I should have mentioned... what was proposed on-list was actually a btrfs-
specific btrfs filesystem du command, paralleling the existing btrfs
filesystem df command...
Unlike the system df command, which AFAIK basically simply prints the
output given to it by the kernel, the system du command does much more of
its own work, stating the files and doing the math itself. And in that
regard, its output is (or should be) accurate.
What the proposed btrfs specific btrfs filesystem du command would do
differently compared to the system command, as is the case with pretty
much all informational btrfs subcommands, is print btrfs specific
information that the system command doesn't. In that regard, it would
be... btrfs specific... and thus belongs under the btrfs master command,
not as part of the normal system command.
Meanwhile, I just looked it up, and posting date was April 23.
Subject: [Patch][RFC] btrfs-progs: add 'du' command
Original poster/author: Mark Fasheh <mfasheh@suse.de>
Link: http://permalink.gmane.org/gmane.comp.file-systems.btrfs/44657
As posted, the patch calculates device (aka disk) usage of the given file
set using fiemap. Printed are device usage, unique/unshared size, and
(for the file set, not individual files) set shared size (the explanation
for which is a bit complex, see the thread). Compression information was
immediately suggested in a reply, but wasn't considered necessary for a
first implementation.
If you're seriously interested, consider reading the thread and replying
there if you have additional suggestions/comments.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2015-05-18 8:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-17 19:33 Btrfs and integration with GNU ++ Roy Sigurd Karlsbakk
2015-05-18 1:32 ` Qu Wenruo
2015-05-18 6:41 ` Duncan
2015-05-18 8:57 ` Duncan [this message]
2015-05-18 9:22 ` Roy Sigurd Karlsbakk
2015-05-18 11:58 ` Austin S Hemmelgarn
2015-05-18 14:31 ` Chris Murphy
2015-05-19 17:09 ` Roy Sigurd Karlsbakk
2015-05-19 18:05 ` Chris Murphy
2015-05-19 18:09 ` Chris Murphy
2015-05-19 19:41 ` Eric Sandeen
2015-05-19 20:04 ` Chris Murphy
2015-05-20 6:45 ` Duncan
2015-05-18 14:24 ` Chris Murphy
2015-05-19 7:24 ` Russell Coker
2015-05-19 11:56 ` Austin S Hemmelgarn
2015-05-19 18:02 ` Chris Murphy
2015-05-20 18:04 ` Zygo Blaxell
2015-05-20 18:02 ` David Sterba
2015-05-18 15:14 ` Eric Sandeen
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='pan$4770b$fa4970d7$3ce3a170$4499f64@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).