Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: Poll: time to switch skinny-metadata on by default?
Date: Tue, 21 Oct 2014 07:02:29 -0400	[thread overview]
Message-ID: <54463D45.1040309@gmail.com> (raw)
In-Reply-To: <pan$32992$bbc3a80d$ad912ad2$31fcc5ce@cox.net>

[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]

On 2014-10-21 05:29, Duncan wrote:
> David Sterba posted on Mon, 20 Oct 2014 18:34:03 +0200 as excerpted:
>
>> On Thu, Oct 16, 2014 at 01:33:37PM +0200, David Sterba wrote:
>>> I'd like to make it default with the 3.17 release of btrfs-progs.
>>> Please let me know if you have objections.
>>
>> For the record, 3.17 will not change the defaults. The timing of the
>> poll was very bad to get enough feedback before the release. Let's keep
>> it open for now.
>
> FWIW my own results agree with yours, I've had no problem with skinny-
> metadata here, and it has been my default now for a couple backup-and-new-
> mkfs.btrfs generations, now.
>
> As you know there were some problems with it in the first kernel cycle or
> two after it was introduced as an option, and I waited awhile until they
> died down before trying it here, but as I said, no problems since I
> switched it on, and I've been running it awhile now.
>
> So defaulting to skinny-metadata looks good from here. =:^)
>
Same here, I've been using it on all my systems since I switched from 
3.15 to 3.16, and have had no issues whatsoever.


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2455 bytes --]

  reply	other threads:[~2014-10-21 11:02 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16 11:33 Poll: time to switch skinny-metadata on by default? David Sterba
2014-10-20 16:34 ` David Sterba
2014-10-21  9:29   ` Duncan
2014-10-21 11:02     ` Austin S Hemmelgarn [this message]
2014-10-21 12:35       ` Konstantinos Skarlatos
2014-10-21 16:40     ` Rich Freeman
2014-10-22  2:08       ` Duncan
2014-10-22 12:49         ` Dave
2014-10-23  2:41           ` Duncan
2014-10-23 13:37             ` David Sterba
2014-10-23 14:47         ` Tobias Geerinckx-Rice
2014-10-24  1:33           ` Duncan
2014-10-25 12:24   ` Marc Joliet
2014-10-25 19:58     ` Marc Joliet
2014-10-27  1:30       ` Marc Joliet
2014-10-25 20:33     ` Chris Murphy
2014-10-25 20:35       ` Chris Murphy
2014-10-27  1:24         ` Marc Joliet
2014-10-27  7:50           ` Duncan
2014-10-27  4:39   ` Zygo Blaxell
2014-10-27  7:16     ` Duncan
  -- strict thread matches above, loose matches on Subject: below --
2014-10-17 12:30 Petr Janecek
2014-10-17 18:25 ` Josef Bacik
2014-10-18 11:21   ` Petr Janecek
2014-10-18 14:04     ` Josef Bacik
2014-10-18 15:52       ` Wang Shilong
2014-10-18 15:53         ` Josef Bacik
2014-10-18 16:01           ` Wang Shilong

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=54463D45.1040309@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=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