Re: read time tree block corruption with kernel 5.4.11

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: read time tree block corruption with kernel 5.4.11
From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
Date: Thu, 16 Jan 2020 02:57:51 +0100
In-reply-to: <f2f96d17-7473-8a24-2702-37e5217ad665@googlemail.com>
References: <f2f96d17-7473-8a24-2702-37e5217ad665@googlemail.com>
User-agent: Evolution 3.34.1-2+b1

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?

Thanks,
Chris.

Follow-Ups:
- Re: read time tree block corruption with kernel 5.4.11
  - From: Oliver Freyermuth

References:
- read time tree block corruption with kernel 5.4.11
  - From: Oliver Freyermuth

Prev by Date: Re: Monitoring not working as "dev stats" returns 0 after read error occurred
Next by Date: Issues with FS going read-only and bad drive?
Previous by thread: Re: read time tree block corruption with kernel 5.4.11
Next by thread: Re: read time tree block corruption with kernel 5.4.11
Index(es):
- Date
- Thread

[Index of Archives] [Linux Filesystem Development] [Linux NFS] [Linux NILFS] [Linux USB Devel] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI]

Powered by Linux