From: cwillu <cwillu@cwillu.com>
To: dave@jikos.cz, Alex <alex@bpmit.com>, linux-btrfs@vger.kernel.org
Subject: Re: (late) REQUEST: Default mkfs.btrfs block size
Date: Mon, 5 Nov 2012 10:25:38 -0600 [thread overview]
Message-ID: <CAE5mzvjKaXki3fPXOMVGt_h6XO+a--J_ADU2AYwz3eCWUgp6XA@mail.gmail.com> (raw)
In-Reply-To: <20121105160649.GM3102@twin.jikos.cz>
On Mon, Nov 5, 2012 at 10:06 AM, David Sterba <dave@jikos.cz> wrote:
> On Wed, Oct 31, 2012 at 12:20:39PM +0000, Alex wrote:
>> As one 'stuck' with 4k leaves on my main machine for the moment, can I request
>> the btrfs-progs v0.20 defaults to more efficient decent block sizes before
>> release. Most distro install programs for the moment don't give access to the
>> options at install time and there seems to be is a significant advantage to 16k
>> or 32k
>
> IMHO this should be fixed inside the installer, changing defaults for a
> core utility will affect everybody. 4k is the most tested option and
> thus can be considered "safe for everybody".
>
> The installer may let you to enter a shell and create the filesystem by
> hand, then point it to use it for installation.
If we know a better setting, we should default to it. Punting the
decision to the distro just means I'll spend the next 3 years telling
people "yeah, distro X doesn't set it to the recommended setting
(which isn't the mkfs default), and there's no way to change it
without wiping and reinstalling using manual partitioning blah blah
blah."
next prev parent reply other threads:[~2012-11-05 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 12:20 (late) REQUEST: Default mkfs.btrfs block size Alex
2012-11-05 16:06 ` David Sterba
2012-11-05 16:25 ` cwillu [this message]
2012-11-08 2:12 ` Dave Chinner
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=CAE5mzvjKaXki3fPXOMVGt_h6XO+a--J_ADU2AYwz3eCWUgp6XA@mail.gmail.com \
--to=cwillu@cwillu.com \
--cc=alex@bpmit.com \
--cc=dave@jikos.cz \
--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).