From: "Michael Kjörling" <michael@kjorling.se>
To: Chris Murphy <chris@colorremedies.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [RFC] New attempt to a better "btrfs fi df"
Date: Sun, 28 Oct 2012 20:09:58 +0000 [thread overview]
Message-ID: <20121028200958.GK2381@yeono.kjorling.se> (raw)
In-Reply-To: <4B78F4E8-C65F-4436-A0BD-147CD776B7A7@colorremedies.com>
On 28 Oct 2012 13:42 -0600, from chris@colorremedies.com (Chris Murphy):
>> * "btrfs" _is_ the file system administration tool. In a way, it makes
>> sense that the data provided by it will be geared more toward
>> technically minded people.
>
> It is a fair point. But this is not LVM or md raid. It's way easier
> to understand and manage already, even with some trouble spots. But
> in the area of storage pool/volume management it's perhaps
> potentially more complex due to subvolumes and actually usable
> snapshots.
>
> So, I must refuse part of the premise that sysadmins and storage
> experts aren't also ordinary people. They can benefit too from
> useful "at a glance" information that, again, doesn't mislead them.
I did not mean to imply that "sysadmins and storage experts aren't
also ordinary people" who can benefit from an "at a glance" view of
their storage situation. Quite to the contrary, that's one point I
have raised in this thread: the usefulness of an "at a glance" view of
the storage situation. But I can also certainly see the side of the
argument that they could reason their way around the concept of raw
storage capacity and allocation multipliers. After all, by the time
you get down to the "a few days of ordinary added data" range of free
space remaining, which would be when the exact numbers _really_ begin
to matter, you should be on top of adding more storage capacity
anyway.
--
Michael Kjörling • http://michael.kjorling.se • michael@kjorling.se
“People who think they know everything really annoy
those of us who know we don’t.” (Bjarne Stroustrup)
next prev parent reply other threads:[~2012-10-28 20:10 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 19:21 [RFC] New attempt to a better "btrfs fi df" Goffredo Baroncelli
2012-10-25 19:40 ` cwillu
2012-10-25 19:59 ` Goffredo Baroncelli
2012-10-25 20:06 ` cwillu
2012-10-25 20:36 ` Chris Murphy
2012-10-25 20:49 ` cwillu
2012-10-25 20:52 ` Goffredo Baroncelli
2012-10-25 20:03 ` Chris Murphy
2012-10-25 20:11 ` cwillu
2012-10-25 20:41 ` Goffredo Baroncelli
2012-10-26 2:33 ` Chris Murphy
2012-10-26 3:36 ` cwillu
2012-10-26 4:03 ` Chris Murphy
2012-10-27 15:05 ` Chris Murphy
2012-10-27 16:43 ` Martin Steigerwald
2012-10-27 19:55 ` Michael Kjörling
2012-10-27 22:30 ` Martin Steigerwald
2012-10-27 22:38 ` Hugo Mills
2012-10-27 23:01 ` Michael Kjörling
2012-10-28 10:58 ` Martin Steigerwald
2012-10-28 8:45 ` Goffredo Baroncelli
2012-10-28 10:38 ` Martin Steigerwald
2012-10-28 10:59 ` Goffredo Baroncelli
2012-10-28 11:18 ` Michael Kjörling
2012-10-28 12:25 ` Goffredo Baroncelli
2012-10-28 12:48 ` Michael Kjörling
2012-10-28 13:22 ` Martin Steigerwald
2012-10-27 23:35 ` Chris Murphy
2012-10-28 11:20 ` Michael Kjörling
2012-10-28 9:01 ` Goffredo Baroncelli
2012-10-28 10:33 ` Martin Steigerwald
2012-10-28 10:58 ` Goffredo Baroncelli
2012-10-28 11:16 ` Martin Steigerwald
2012-10-28 18:27 ` Chris Murphy
2012-10-28 19:06 ` Michael Kjörling
2012-10-28 19:42 ` Chris Murphy
2012-10-28 20:09 ` Michael Kjörling [this message]
2012-10-28 20:19 ` Chris Murphy
2012-10-29 9:04 ` Michael Kjörling
2012-10-30 4:41 ` Chris Murphy
2012-10-28 19:42 ` Chris Murphy
2012-10-29 13:06 ` Randy Barlow
2012-10-29 22:21 ` [RFC][V2] " Goffredo Baroncelli
2012-10-30 9:42 ` Michael Kjörling
2012-10-30 18:15 ` Goffredo Baroncelli
2012-10-30 18:32 ` Michael Kjörling
2012-10-30 20:13 ` Chris Murphy
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=20121028200958.GK2381@yeono.kjorling.se \
--to=michael@kjorling.se \
--cc=chris@colorremedies.com \
--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