All of lore.kernel.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: downgrade from kernel 3.17 to 3.10
Date: Tue, 21 Oct 2014 11:26:53 +0000 (UTC)	[thread overview]
Message-ID: <pan$e55c6$e7985780$d6580cb2$76eb6d4@cox.net> (raw)
In-Reply-To: CAMo7R_e9=wdGhEm9P+DZgXrKQ+qrKqdELzwwi-OMTCp6Mk8aTg@mail.gmail.com

Cristian Falcas posted on Tue, 21 Oct 2014 11:13:48 +0300 as excerpted:

> 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 mean, is there something that could go wrong with the fs if suddenly I
> use an older kernel?
> 
> I want to downgrade because last night we had some 1200 oops's in 1 hour
> on the 3.17 kernel related to "CPU#n stuck" and what seems to be btrfs
> work:

You definitely don't want to downgrade that far -- there's way too many 
btrfs fixes since then and you'd be needlessly risking your data.

Much more viable would be to downgrade to the latest 3.16.x stable kernel 
(definitely not 3.16.0 or 3.16.1 as they had an open issue much like 
3.17.0 does), and then upgrade to the latest 3.17.x in a couple weeks, as 
there's some critical stable fixes in the pipeline for it.

Or if you must, 3.14.x is the latest long-term-stable series, and is 
continuing to get btrfs-stable patches along with the other stable 
patches it gets.

But I'd definitely not recommend reverting to older than 3.14.x stable 
series, because even if it's a stable series and they catch and apply to 
stable all the patches that ideally need to be applied back that far, if 
you have problems, what you'd be running is simply too far back in 
history to get much support on this list for.

Also, keep in mind that the btrfs-is-experimental warnings didn't come 
off until 3.12 or so.  Any btrfs older than that was officially 
experimental when it came out, and even if it's a long-term-stable 
kernel, no stable series patches are going to remove the still 
experimental nature of btrfs in a kernel that old.

So 3.10, no way if it were /my/ data!  Latest 3.14.x stable, I'd 
consider.  But preferably step back to the latest 3.16.x (past 3.16.2 for 
sure) temporarily, and try latest 3.17.x again in a couple weeks (or 3.18-
live-git now) as there's some critical fixes for 3.17-stable now in 3.18 
and still making their way to the stable releases.

-- 
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:[~2014-10-21 11:27 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 [this message]
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

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$e55c6$e7985780$d6580cb2$76eb6d4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.