From: Robert White <rwhite@pobox.com>
To: Cristian Falcas <cristi.falcas@gmail.com>, Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: downgrade from kernel 3.17 to 3.10
Date: Tue, 21 Oct 2014 08:20:30 -0700 [thread overview]
Message-ID: <544679BE.9080901@pobox.com> (raw)
In-Reply-To: <CAMo7R_egQMGXs4nJBPkp86QkF9owpUhAh6P_Vn65wN84J7B95w@mail.gmail.com>
On 10/21/2014 06:18 AM, Cristian Falcas wrote:
> Thank you for your answer.
>
> I will reformat the disk with a 3.10 kernel in the meantime, because I
> don't have any rpms for 3.16 now.
More concisely: Don't use 3.10 BTRFS for data you value. There is a
non-trivial chance that the problems you observed are/were due to "bad
things" on the disk written there by 3.10.
There is no value to recreating your file systems under 3.10 as the same
thing is likely to go bad again when you get out of the dungeon.
What are your RPM options? What about just getting the sources from
kernel.org and compiling your won 3.16.5?
Seriously, 3.10.... just... no...
8-)
next prev parent reply other threads:[~2014-10-21 15:20 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 [this message]
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=544679BE.9080901@pobox.com \
--to=rwhite@pobox.com \
--cc=1i5t5.duncan@cox.net \
--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 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.