From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Small fs
Date: Mon, 12 Sep 2016 02:00:04 +0000 (UTC) [thread overview]
Message-ID: <pan$e206f$d515790a$646cc891$9e1c047e@cox.net> (raw)
In-Reply-To: CAJCQCtT5T5M7a1vtaGZjGLiPs_6-MnMXc5qPoH0Hc7RJPz0HZw@mail.gmail.com
Chris Murphy posted on Sun, 11 Sep 2016 14:33:18 -0600 as excerpted:
> Something else that's screwy in that bug that I just realized, why is it
> not defaulting to mixed-block groups on a 100MiB fallocated file? I
> thought mixed-bg was the default below a certain size like 2GiB or
> whatever?
You apparently missed the memo...
Newer btrfs-progs mkfs.btrfs no longer defaults under-1-GiB to mixed-bg
mode, tho it remains very strongly recommended below 1 GiB, and soft-
recommended to somewhere between 4 and 32 GiB (I believe the wiki says 5
GiB at this point but don't know how it arrived at that, but the numbers
I've seen suggested on-list range between 4 and 32 GiB, as above).
The explanation of why, based on the thread where I remember it coming
up, was because defaulting to mixed-mode was making testing more
complex. Don't ask me to agree with that because I most certainly don't;
IMO sane defaults for normal use, which everyone seems to agree mixed-
mode for under a GiB is, should apply, and if testing needs special-
cased, well, special-case it. But none-the-less, that's the context in
which it was agreed to do away with the mixed-mode default, despite it
still being extremely strongly recommended for under a GiB. <shrug>
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2016-09-12 2:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 15:27 Small fs Imran Geriskovan
2016-09-11 15:32 ` Martin Steigerwald
2016-09-11 16:44 ` Duncan
2016-09-11 18:56 ` Imran Geriskovan
2016-09-11 19:21 ` Martin Steigerwald
2016-09-12 12:41 ` Austin S. Hemmelgarn
2016-09-12 14:09 ` Henk Slager
2016-09-12 14:12 ` Austin S. Hemmelgarn
2016-09-12 14:51 ` Chris Murphy
2016-09-12 14:56 ` Austin S. Hemmelgarn
2016-09-12 3:33 ` Duncan
2016-09-12 14:11 ` Imran Geriskovan
2016-09-12 17:43 ` Imran Geriskovan
2016-09-12 18:46 ` Imran Geriskovan
2016-09-12 18:55 ` Austin S. Hemmelgarn
2016-09-12 21:32 ` Mike Fleetwood
2016-09-11 19:13 ` Martin Steigerwald
2016-09-11 19:46 ` Hugo Mills
2016-09-11 19:51 ` Martin Steigerwald
2016-09-12 12:45 ` Austin S. Hemmelgarn
2016-09-11 20:33 ` Chris Murphy
2016-09-12 2:00 ` Duncan [this message]
2016-09-12 3:03 ` Chris Murphy
2016-09-12 4:54 ` Duncan
2016-09-12 14:48 ` Chris Murphy
2016-09-13 4:25 ` Duncan
2016-09-12 12:54 ` Imran Geriskovan
2016-09-12 13:01 ` Austin S. Hemmelgarn
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='pan$e206f$d515790a$646cc891$9e1c047e@cox.net' \
--to=1i5t5.duncan@cox.net \
--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.