Re: Massive filesystem corruption after balance + fstrim on Linux 5.1.2

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

Subject: Re: Massive filesystem corruption after balance + fstrim on Linux 5.1.2
From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
Date: Tue, 28 May 2019 14:36:37 +0200
In-reply-to: <297da4cbe20235080205719805b08810@bi-co.net>
References: <297da4cbe20235080205719805b08810@bi-co.net>
User-agent: Evolution 3.30.5-1

Hey.

Just to be on the safe side...

AFAIU this issue only occured in 5.1.2 and later, right?

Starting with which 5.1.x and 5.2.x versions has the fix been merged?

Cheers,
Chris.

Follow-Ups:
- Re: Massive filesystem corruption after balance + fstrim on Linux 5.1.2
  - From: Michael Laß

References:
- Massive filesystem corruption after balance + fstrim on Linux 5.1.2
  - From: Michael Laß

Prev by Date: Re: parent transid verify failed on 604602368 wanted 840641 found 840639
Next by Date: Re: Massive filesystem corruption after balance + fstrim on Linux 5.1.2
Previous by thread: Re: fstrim discarding too many or wrong blocks on Linux 5.1, leading to data loss
Next by thread: Re: Massive filesystem corruption after balance + fstrim on Linux 5.1.2
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