From: "Agustín DallʼAlba" <agustin@dallalba.com.ar>
To: Martin Steigerwald <martin@lichtvoll.de>,
linux-btrfs@vger.kernel.org, Nikolay Borisov <nborisov@suse.com>
Subject: Re: raid10 corruption while removing failing disk
Date: Mon, 10 Aug 2020 04:59:57 -0300 [thread overview]
Message-ID: <75b06c6a26cf64bd9d2eeb76bf81ea698126257e.camel@dallalba.com.ar> (raw)
In-Reply-To: <16328609.DpnNoz7ane@merkaba>
On Mon, 2020-08-10 at 09:38 +0200, Martin Steigerwald wrote:
> I have no idea why Ubuntu opted to use a non LTS kernel – especially as
> 4.15 is pretty old and so does not sound to come from a supported Ubuntu
> release unless it is some Ubuntu LTS release, but then I'd expect a LTS
> kernel to be used –, but "-111" indicates they added a lot of patches by
> now. So maybe they provide some kind of LTS support themselves.
It is indeed the kernel of the 18.04 LTS Ubuntu release.
On Mon, 2020-08-10 at 10:22 +0300, Nikolay Borisov wrote:
> This is a vendor kernel so you should ideally seek support through the
> vendor. This kernel is not even an LTS so it's not entirely clear which
> patches have/have not been backported. With btrfs it's advisable too use
> the latest stable kernel as each release brings bug fixes or at the very
> least (because always using the latest is not feasible) at least stick
> to a supported long-term stable kernel - i.e 4.14, 4.19 or 5.4
> (preferably 5.4)
Would it help to run a mainline kernel and report again, or is it 'too
late' for this filesystem? If so, should I use 5.4.57 or go straight to
5.8? For now I have forwarded my question to the Ubuntu kernel team
mailing list.
Kind regards.
next prev parent reply other threads:[~2020-08-10 8:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 7:03 raid10 corruption while removing failing disk Agustín DallʼAlba
2020-08-10 7:22 ` Nikolay Borisov
2020-08-10 7:38 ` Martin Steigerwald
2020-08-10 7:51 ` Nikolay Borisov
2020-08-10 8:57 ` Martin Steigerwald
2020-08-11 1:30 ` Chris Murphy
2020-08-10 7:59 ` Agustín DallʼAlba [this message]
2020-08-10 8:21 ` Nikolay Borisov
2020-08-10 22:24 ` Zygo Blaxell
2020-08-11 1:18 ` Agustín DallʼAlba
2020-08-11 1:48 ` Chris Murphy
2020-08-11 2:34 ` Chris Murphy
2020-08-11 5:06 ` Agustín DallʼAlba
2020-08-11 19:17 ` Chris Murphy
2020-08-11 20:40 ` Agustín DallʼAlba
2020-08-12 3:03 ` Chris Murphy
2020-08-31 20:05 ` Agustín DallʼAlba
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=75b06c6a26cf64bd9d2eeb76bf81ea698126257e.camel@dallalba.com.ar \
--to=agustin@dallalba.com.ar \
--cc=linux-btrfs@vger.kernel.org \
--cc=martin@lichtvoll.de \
--cc=nborisov@suse.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 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.