linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Hugo Mills <hugo@carfax.org.uk>
Cc: Jon Keane <jkeane@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Unmountable btrfs after power failure
Date: Wed, 9 Sep 2015 22:27:13 +0500	[thread overview]
Message-ID: <20150909222713.60d7d9de@natsu> (raw)
In-Reply-To: <20150909171951.GQ23944@carfax.org.uk>

[-- Attachment #1: Type: text/plain, Size: 858 bytes --]

On Wed, 9 Sep 2015 17:19:51 +0000
Hugo Mills <hugo@carfax.org.uk> wrote:

>    The bug you've hit is almost certainly fixed in more recent
> kernels. I can't recommend stongly enough that you upgrade it (or
> contact your vendor's support department to find out how they will
> support your use of btrfs on a kernel that old). 3.19 is about the
> earliest kernel I'd feel happy about using at this point.

3.19 is EOL and is not featured on https://www.kernel.org/ anymore.

I hope 3.18 is also good enough, for those of us who prefer to stay on a
"longterm" kernel and not jump every time onto a new series only to find out
that it's in fact destined to go into the EOL trashcan. (There's a certain
amount of tinkering with the .config required each time when switching
releases, and I'd like to minimize that).

-- 
With respect,
Roman

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2015-09-09 17:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-09 15:30 Unmountable btrfs after power failure Jon Keane
2015-09-09 17:19 ` Hugo Mills
2015-09-09 17:27   ` Roman Mamedov [this message]
2015-09-09 21:32     ` Jon Keane

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=20150909222713.60d7d9de@natsu \
    --to=rm@romanrm.net \
    --cc=hugo@carfax.org.uk \
    --cc=jkeane@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;
as well as URLs for NNTP newsgroup(s).