From: jim owens <jowens@hp.com>
To: Josef Bacik <josef@redhat.com>, Roland Dreier <rdreier@cisco.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: UI issues around RAID1
Date: Mon, 16 Nov 2009 16:48:31 -0500 [thread overview]
Message-ID: <4B01C8AF.5040308@hp.com> (raw)
In-Reply-To: <20091116202043.GA9779@localhost.localdomain>
Josef Bacik wrote:
> On Mon, Nov 16, 2009 at 10:45:28AM -0800, Roland Dreier wrote:
>> - The free space reporting doesn't seem to take into account the fact
>> that everything is going to be mirrored; so "df" et al report the
>> size of the filesystem and free space on the new filesystem as
>> size(dev1) + size(dev2) -- if dev1 and dev2 are the same size then I
>> would assume it should really be just size(dev1) for a fully-RAID1
>> filesystem. (Not sure in general what we should say for a
>> metadata-only mirrored filesystem, since we don't really know in
>> advance how much space we have exactly)
>>
>
> Yeah df is just a fun ball of wax in many respects. We don't take into account
> RAID and we don't subtrace space thats strictly for metadata, so there are
> several things that need to be fixed for df. Thanks,
But as we have said many times... if we have different
raid types active on different files, any attempt to make
df report "raid adjusted numbers" instead of the current raw
total storage numbers is going to sometimes give wrong answers.
So I think it is dangerous to try. The current output
may be ugly, but it is always consistent and explainable.
jim
next prev parent reply other threads:[~2009-11-16 21:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 18:45 UI issues around RAID1 Roland Dreier
2009-11-16 20:20 ` Josef Bacik
2009-11-16 21:48 ` jim owens [this message]
[not found] ` <2a31deca0911170244m74478cefy2a3f5f7bc1daf476@mail.gmail.com>
2009-11-17 15:25 ` jim owens
2009-11-17 20:23 ` Andrey Kuzmin
2009-11-18 17:59 ` Roland Dreier
2009-11-19 14:56 ` Chris Mason
2009-11-18 17:54 ` Roland Dreier
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=4B01C8AF.5040308@hp.com \
--to=jowens@hp.com \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rdreier@cisco.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