Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs progs pre-release 4.3-rc1
Date: Tue, 3 Nov 2015 00:10:14 +0000 (UTC)	[thread overview]
Message-ID: <pan$92b40$752beab9$f06026e1$b913018c@cox.net> (raw)
In-Reply-To: 20151102151453.GI13624@twin.jikos.cz

David Sterba posted on Mon, 02 Nov 2015 16:14:53 +0100 as excerpted:

> 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

It says one change in the /defaults/, but then it says mixed mode isn't 
/forced/ anymore under a GiB.

Which is it, a change in the /defaults/, under a gig now defaults to 
separate data/metadata, or same /defaults/, but now there's a way to 
overrule them and do separate data/metadata under a gig, so while mixed 
remains the default, it's no longer /forced/?

If the /defaults/ changed, is mixed mode still /recommended/ for small 
filesystems?

-- 
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


  reply	other threads:[~2015-11-03  0:10 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 [this message]
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

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$92b40$752beab9$f06026e1$b913018c@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox