From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Chris Murphy <lists@colorremedies.com>,
dsterba@suse.cz, Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
Chris Mason <clm@fb.com>
Subject: Re: Btrfs progs pre-release 4.3-rc1
Date: Mon, 9 Nov 2015 08:29:09 -0500 [thread overview]
Message-ID: <56409FA5.1060802@gmail.com> (raw)
In-Reply-To: <CAJCQCtT1XxVqJ70j-NQ_-eLZTHvF66=8-0Xg=uo39=cg4=fwZg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
On 2015-11-07 08:58, Chris Murphy wrote:
> On Mon, Nov 2, 2015 at 4:14 PM, David Sterba <dsterba@suse.cz> wrote:
>> Hi,
>>
>> the kernel 4.3 was released yesterday, the btrfs-progs will follow at the end
>> of this week. I've tagged an rc1 from current devel branch. There are a lots of
>> small invisible changes and one change in the defaults:
>>
>> * mkfs: mixed mode is not forced anymore for devices smaller than 1 GiB
>
> Why?
>
> If it's still recommended to use mixed for small device, why not keep
> it the default and just permit the user to manually specify something
> else?
>
I think the reasoning here is that leaving it as the default would
require adding another option (possibly, I don't know if -O !mixed-bg
works to override the default). Of course, properly educating people
that they should be using this on small devices is going to be a much
longer and more involved task than just adding an option...
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
prev parent reply other threads:[~2015-11-09 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 15:14 Btrfs progs pre-release 4.3-rc1 David Sterba
2015-11-03 0:10 ` Duncan
2015-11-06 10:53 ` David Sterba
2015-11-07 8:34 ` Duncan
2015-11-07 13:58 ` Chris Murphy
2015-11-09 13:29 ` Austin S Hemmelgarn [this message]
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=56409FA5.1060802@gmail.com \
--to=ahferroin7@gmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox