public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
To: Brad Templeton <4brad@templetons.com>
Cc: Andrei Borzenkov <arvidjaar@gmail.com>,
	Tomasz Chmielewski <mangoo@wpkg.org>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-transacti hangs system for several seconds every few minutes
Date: Tue, 31 Mar 2020 00:20:50 -0400	[thread overview]
Message-ID: <20200331042050.GE13306@hungrycats.org> (raw)
In-Reply-To: <b71b10f8-6410-4d32-f89c-9b3f20d9b2f2@templetons.com>

On Mon, Mar 30, 2020 at 01:11:41AM -0700, Brad Templeton wrote:
> Also, isn't it 4 debs -- image, modules, headers and architecture
> independent headers?
> 
> Still, I am surprised that the ubuntu team, with a data corruption
> issue, would not make a priority to install a fixed kernel or at least
> backport btrfs modules into the current kernel.

It probably hasn't been reported to them.  Distro vendors are kind of
on their own for long-term kernel bug fixes, especially for non-LTS
kernels like 5.3.  kernel.org support ended last year, just before the
bug was identified.

> On 3/29/20 10:56 PM, Andrei Borzenkov wrote:
> > 30.03.2020 05:29, Tomasz Chmielewski пишет:
> >>> I wonder why they put 5.3.0 as the standard advanced Kernel in Ubuntu
> >>> LTS if it has a data corruption bug.   I don't know if I've seen any
> >>> release of 5.4.14 in a PPA yet -- manual kernel install is such a pain
> >>> the few times I have done it.
> >>
> >> You have all kernels compiled as packages here (for Ubuntu):
> >>
> >> https://kernel.ubuntu.com/~kernel-ppa/mainline/
> >>
> >> So just download two deb packages, dpkg -i, and done.
> >>
> > 
> > Beware that it is not exactly the same as distribution kernel (both in
> > terms of included patches and enabled configuration options). Also
> > matching linux-tools is not provided which means perf, cpupower,
> > turbostat and some other tools stop working.
> > 

  parent reply	other threads:[~2020-03-31  4:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-30  2:29 btrfs-transacti hangs system for several seconds every few minutes Tomasz Chmielewski
2020-03-30  5:56 ` Andrei Borzenkov
2020-03-30  8:11   ` Brad Templeton
2020-03-30  8:35     ` Tomasz Chmielewski
2020-03-31  4:20     ` Zygo Blaxell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-03-29  4:03 Brad Templeton
2020-03-29 13:14 ` Qu Wenruo
2020-03-29 17:58   ` Brad Templeton
2020-03-29 18:09     ` Zygo Blaxell
2020-03-28 18:26 Brad Templeton
2020-03-28 21:20 ` Zygo Blaxell
     [not found]   ` <7778ece0-67d4-8d1c-b773-35f07d81dcbe@templetons.com>
2020-03-29  6:42     ` Zygo Blaxell
2020-03-30 22:14       ` Chris Murphy
2020-03-31  4:04         ` Zygo Blaxell
2020-03-29  0:58 ` Qu Wenruo

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=20200331042050.GE13306@hungrycats.org \
    --to=ce3g8jdj@umail.furryterror.org \
    --cc=4brad@templetons.com \
    --cc=arvidjaar@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mangoo@wpkg.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