From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Poll: time to switch skinny-metadata on by default?
Date: Fri, 24 Oct 2014 01:33:39 +0000 (UTC) [thread overview]
Message-ID: <pan$c6d4f$2fb03bde$c07e7d4a$f7039042@cox.net> (raw)
In-Reply-To: CAKFHe2RxEZo25+3ye6fLmfadSbVZ5rri8h_FPt5iAy3-AiSqPQ@mail.gmail.com
Tobias Geerinckx-Rice posted on Thu, 23 Oct 2014 16:47:19 +0200 as
excerpted:
> On 22 October 2014 04:08, Duncan <1i5t5.duncan@cox.net> wrote:
>
>> Since the kernel has code for both "fat" metadata and skinny-metadata,
>> they can exist side-by-side and the kernel will use whichever code is
>> appropriate.
>
> I understand that the fat extent code will probably never be removed for
> compatibility reasons, but do wonder why it's still the default.
> Caution?
Caution, backward kernel compatibility, and simply timing.
The skinny code is newer, and there were several skinny-metadata related
bugs in the first couple kernel cycles it was available, so not making it
the immediate default was certainly wise. Tho the new code has been
reasonably stable for awhile, now. But that's exactly why this
discussion, is it time to make the new code the default yet, or not,
because it hasn't been done yet.
Additionally, some people want to keep the flexibility to mount with old
kernels. Consider a distro installation and rescue image (ISO or USB),
for instance. Those can be used for rescue purposes for not only the
life of that distro release, but for sometime afterward. If the only
rescue image you can find is a two year old image and it won't mount your
btrfs because the on-device format has changed since then and your
filesystem is the newer format, you're going to be one frustrated btrfs
user!
> Petr Janecek's balancing problem [1] and similar bugs aside: is there a
> functional reason to prefer "fat" over skinny metadata for future file
> systems?
Other than keeping backward compatibility to work with old rescue images
and the like, as discussed above, not that I'm aware of. IOW, I know of
no corner-case where fat metadata is now more efficient or more stable.
--
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:[~2014-10-24 1:33 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
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 [this message]
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='pan$c6d4f$2fb03bde$c07e7d4a$f7039042@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