All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Freyermuth <o.freyermuth@googlemail.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>,
	linux-btrfs@vger.kernel.org
Subject: Re: read time tree block corruption with kernel 5.4.11
Date: Thu, 16 Jan 2020 04:37:47 +0100	[thread overview]
Message-ID: <3778c13f-a0b3-70d3-a09f-ce704e5c01fc@googlemail.com> (raw)
In-Reply-To: <ba2dcbb0085b186c6df859a4f5db415597fe2f8e.camel@scientia.net>

Dear Chris,

Am 16.01.20 um 02:57 schrieb Christoph Anton Mitterer:
> On Wed, 2020-01-15 at 23:04 +0100, Oliver Freyermuth wrote:
>> I have recently upgraded to 5.4.11 from a 5.3 kernel and now also hit
>> the dreaded read time tree block corruption
> 
> Is there some known corruption bug in 5.4?

I don't think so / don't know, but the tree checker became more sensitive as compared to 5.3, so I dreaded this message after I saw the density of such reports
from other users growing on the list in the past months. 

My only overlap with an earlier report seems to be that I had a situation of high memory pressure in the past weeks on the machine. 
Two other machines I run with very similar setups and significantly longer runtimes have not shown any issues. 

The affected node has the lowest runtime of the three, "but it ran fine with Kernel 5.4 for a while" and now suddenly detected the corruption in old data extens quickly after bootup.
I don't find any issues with memtext86+. 
So I'll keep an eye on the machine. At this point, anything else would be guesswork. 

Cheers,
	Oliver

      reply	other threads:[~2020-01-16  3:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15 22:04 read time tree block corruption with kernel 5.4.11 Oliver Freyermuth
2020-01-16  0:56 ` Qu Wenruo
2020-01-16  3:31   ` Oliver Freyermuth
2020-01-16  3:45     ` Qu Wenruo
2020-01-16  1:57 ` Christoph Anton Mitterer
2020-01-16  3:37   ` Oliver Freyermuth [this message]

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=3778c13f-a0b3-70d3-a09f-ce704e5c01fc@googlemail.com \
    --to=o.freyermuth@googlemail.com \
    --cc=calestyo@scientia.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.