From: Hugo Mills <hugo@carfax.org.uk>
To: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: mkfs.btrfs/balance small-btrfs chunk size RFC
Date: Tue, 10 Jan 2017 15:47:53 +0000 [thread overview]
Message-ID: <20170110154753.GK19585@carfax.org.uk> (raw)
In-Reply-To: <c934f74c-6dac-b66f-13cf-eb9bf0a79aac@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
On Tue, Jan 10, 2017 at 10:42:51AM -0500, Austin S. Hemmelgarn wrote:
> Most of the issue in this case is with the size of the initial
> chunk. That said, I've got quite a few reasonably sized filesystems
> (I think the largest is 200GB) with moderate usage (max 90GB of
> data), and none of them are using more than the first 16kB block in
> the System chunk. While I'm not necessarily a typical user, I'd be
> willing to bet based on this that in general, most people who aren't
> storing very large amounts of data or taking huge numbers of
> snapshots aren't going to need a system chunk much bigger than 1MB.
Again, the system chunk has *nothing* to do with snapshots.
Agreed with everything else, though.
Hugo.
--
Hugo Mills | I'm always right. But I might be wrong about that.
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2017-01-10 15:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 3:55 mkfs.btrfs/balance small-btrfs chunk size RFC Duncan
2017-01-10 5:34 ` Qu Wenruo
2017-01-10 14:57 ` Austin S. Hemmelgarn
2017-01-10 15:29 ` Hugo Mills
2017-01-10 15:42 ` Austin S. Hemmelgarn
2017-01-10 15:47 ` Hugo Mills [this message]
2017-01-10 16:05 ` Austin S. Hemmelgarn
2017-01-10 16:10 ` Hugo Mills
2017-01-11 19:00 ` Duncan
2017-01-10 17:17 ` Austin S. Hemmelgarn
2017-01-11 19:25 ` Duncan
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=20170110154753.GK19585@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=ahferroin7@gmail.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;
as well as URLs for NNTP newsgroup(s).