From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Vytautas D <vytdau@gmail.com>, Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: upgrading kernel 3.13 to 3.16
Date: Fri, 26 Feb 2016 07:14:36 -0500 [thread overview]
Message-ID: <56D041AC.6070802@gmail.com> (raw)
In-Reply-To: <CAO5K3OdzXgXpSNqCOqvMwVgQWiEF9p91ymB+uXjFRCCK24QWZg@mail.gmail.com>
On 2016-02-26 05:50, Vytautas D wrote:
> Hi all,
>
> Are there any known issues upgrading btrfs running ubuntu kernel 3.13
> to 3.16 ? System was once converted from ext4 using btrfs-convert (
> btrfs-progs 3.17 ).
>
> The commit that worries me is following:
> * Btrfs: incompatible format change to remove hole extents (+373/-56)
> ( http://linux-btrfs.vger.kernel.narkive.com/syNRZbHS/patch-btrfs-incompatible-format-change-to-remove-hole-extents-v3#post1
> )
>
> would this block me from reverting system with a snapshot back to kernel 3.13 ?
> After upgrade would the system continue writing more metadata ?
That particular commit also added a flag to control whether or not newly
written metadata uses that feature. As long as you don't manually
enable this flag, you should be perfectly fine WRT that change.
next prev parent reply other threads:[~2016-02-26 12:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 10:50 upgrading kernel 3.13 to 3.16 Vytautas D
2016-02-26 12:14 ` Austin S. Hemmelgarn [this message]
2016-02-26 21:07 ` Duncan
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=56D041AC.6070802@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=vytdau@gmail.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;
as well as URLs for NNTP newsgroup(s).