From: Goffredo Baroncelli <kreijack@inwind.it>
To: ashford@whisperpc.com
Cc: Shriramana Sharma <samjnaa@gmail.com>,
Martin Steigerwald <martin@lichtvoll.de>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Why is the actual disk usage of btrfs considered unknowable?
Date: Mon, 08 Dec 2014 00:01:16 +0100 [thread overview]
Message-ID: <5484DC3C.7040409@inwind.it> (raw)
In-Reply-To: <6554b2b132dd3f9803bcf8c10f11a156.squirrel@webmail.wanet.net>
On 12/07/2014 09:32 PM, ashford@whisperpc.com wrote:
>> In conclusion, the disk usage is well known; which is unknown is
>> > the space that is available to the user (who is uninterested to
>> > all the details inside a filesystem). The best that is doable
>> > is an estimation like the above one.
> I disagree. My experiences with other file-systems, including ZFS, show
> that the most common solution is to just deliver to the user the actual
> amount of unused disk space. Anything else changes this known value into
> a guess or prediction.
So in case you have a raid1 filesystem on two disks; each disk has 300GB
free; which is the free space that you expected: 300GB or 600GB and why ?
>
> Peter Ashford
BR
G.Baroncelli
>
>
--
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:[~2014-12-07 23:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-07 15:15 Why is the actual disk usage of btrfs considered unknowable? Shriramana Sharma
2014-12-07 15:33 ` Martin Steigerwald
2014-12-07 15:37 ` Shriramana Sharma
2014-12-07 15:40 ` Martin Steigerwald
2014-12-08 5:32 ` Robert White
2014-12-08 6:20 ` ashford
2014-12-08 7:06 ` Robert White
2014-12-08 14:47 ` Martin Steigerwald
2014-12-08 14:57 ` Austin S Hemmelgarn
2014-12-08 15:52 ` Martin Steigerwald
2014-12-08 23:14 ` Zygo Blaxell
2014-12-07 18:20 ` ashford
2014-12-07 18:34 ` Hugo Mills
2014-12-07 18:48 ` Martin Steigerwald
2014-12-07 19:39 ` ashford
2014-12-08 5:17 ` Chris Murphy
2014-12-07 18:38 ` Martin Steigerwald
2014-12-07 19:44 ` ashford
2014-12-07 19:19 ` Goffredo Baroncelli
2014-12-07 20:32 ` ashford
2014-12-07 23:01 ` Goffredo Baroncelli [this message]
2014-12-08 0:12 ` ashford
2014-12-08 2:42 ` Qu Wenruo
2014-12-08 8:12 ` ashford
2014-12-08 14:34 ` Goffredo Baroncelli
2014-12-08 8:18 ` Chris Murphy
2014-12-08 4:59 ` Robert White
2014-12-08 6:43 ` Zygo Blaxell
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=5484DC3C.7040409@inwind.it \
--to=kreijack@inwind.it \
--cc=ashford@whisperpc.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=martin@lichtvoll.de \
--cc=samjnaa@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 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.