Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Robert White <rwhite@pobox.com>
To: Cristian Falcas <cristi.falcas@gmail.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: downgrade from kernel 3.17 to 3.10
Date: Tue, 21 Oct 2014 08:04:23 -0700	[thread overview]
Message-ID: <544675F7.3010808@pobox.com> (raw)
In-Reply-To: <CAMo7R_e9=wdGhEm9P+DZgXrKQ+qrKqdELzwwi-OMTCp6Mk8aTg@mail.gmail.com>

On 10/21/2014 01:13 AM, Cristian Falcas wrote:
> Can I downgrade the kernel from 3.17.1 to latest 3.10 if I have a
> btrfs partition formatted and used on 3.17.1?

I went back from 3.17.0 to 3.16.3 when 3.17 acted flaky, and since then 
gone up to 3.16.5 with nice results. 3.17.2 is, I think, expected to 
contain the actual fixes

Did you upgrade straight from 3.10 to 3.17?

Going all the way back to 3.10 is probably a bad thing. There's been a 
lot of work since then. I'd build a new 3.16.5 and switch to that.

DONT go back further, and DONT run btrfsck until the mainline and tools 
that fix the "read-only snapshot bug" are in your system. I think that's 
going to be 3.17.2 and the 3.17 btrfs tools. If you use older tools you 
may end up having to recreate the partition completely.




      parent reply	other threads:[~2014-10-21 15:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21  8:13 downgrade from kernel 3.17 to 3.10 Cristian Falcas
2014-10-21 11:26 ` Duncan
2014-10-21 13:18   ` Cristian Falcas
2014-10-21 15:13     ` Robert White
2014-10-21 15:20     ` Robert White
2014-10-21 15:34       ` Cristian Falcas
2014-10-21 15:58         ` Austin S Hemmelgarn
2014-10-21 16:19         ` Chris Murphy
2014-10-21 16:26           ` Chris Murphy
2014-10-21 16:36         ` Julio E. Gonzalez P.
2014-10-21 17:55           ` Cristian Falcas
2014-10-21 16:07     ` Chris Murphy
2014-10-22  2:24       ` Duncan
2014-10-21 15:04 ` Robert White [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=544675F7.3010808@pobox.com \
    --to=rwhite@pobox.com \
    --cc=cristi.falcas@gmail.com \
    --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