From: Goffredo Baroncelli <kreijack@gmail.com>
To: Brendan Hide <brendan@swiftspirit.co.za>
Cc: linux-btrfs Mailing list <linux-btrfs@vger.kernel.org>,
Chris Mason <chris.mason@fusionio.com>
Subject: Re: btrfs df confusion
Date: Thu, 27 Dec 2012 18:04:00 +0100 [thread overview]
Message-ID: <50DC7F80.4060409@gmail.com> (raw)
In-Reply-To: <50DC3807.9080605@swiftspirit.co.za>
On 12/27/2012 12:59 PM, Brendan Hide wrote:
> Hi
Hi,
>
> I've made some updates on the wiki and I'd like a technical review for
> correctness. This particular topic is already confusing - some
> unnecessary sarcasm made it even more so:
> https://btrfs.wiki.kernel.org/index.php/FAQ#Why_does_df_show_incorrect_free_space_for_my_RAID_volume.3F
I posted some patches in order to address this issue. However these
aren't integrated (yet). At the end I think that I reached a general
consensus about the wording. A general description is here [1]. The
patch related to man page is here [2], which can help about the wording.
I hope that it will help your work.
BR
G.Baroncelli
>
>
> Due to the terms "used" and "allocated" in the wiki, viric in #btrfs
> made the good suggestion that we could adjust the show and df output
> with more intuitive language:
>
> Before I git a patch together, please let me know if there are any good
> reasons why we wouldn't want to make such a change.
>
> (13:31:29) viric: zatricky: "devid ... used" are allocated data, while
> "FS bytes used" is the sum of used bytes, isn't it?
> (13:33:28) zatricky: viric: correct
> (13:33:52) viric: zatricky: maybe the devid lines could be changed
> s/used/allocated/
> (13:34:37) zatricky: viric: that's a good idea - would make it more
> intuitive
> (13:35:29) viric: the same way, 'btrfs fi df' could change
> s/total/allocated
> ^ GMT+2 ;)
>
> Thanks
>
[1] http://permalink.gmane.org/gmane.comp.file-systems.btrfs/21071
[2]
http://markmail.org/thread/nol2gcjky4cxndhv#query:+page:1+mid:xqnyqp7slb7rrach+state:results
--
gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2012-12-27 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 11:59 btrfs df confusion Brendan Hide
2012-12-27 17:04 ` Goffredo Baroncelli [this message]
2012-12-27 22:28 ` Brendan Hide
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=50DC7F80.4060409@gmail.com \
--to=kreijack@gmail.com \
--cc=brendan@swiftspirit.co.za \
--cc=chris.mason@fusionio.com \
--cc=kreijack@inwind.it \
--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 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.