From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.wl.linuxfoundation.org ([198.145.29.98]:36114 "EHLO mail.wl.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726355AbeK3QJI (ORCPT ); Fri, 30 Nov 2018 11:09:08 -0500 Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 0E6012FEED for ; Fri, 30 Nov 2018 05:01:05 +0000 (UTC) From: bugzilla-daemon@bugzilla.kernel.org To: linux-ext4@vger.kernel.org Subject: [Bug 201685] ext4 file system corruption Date: Fri, 30 Nov 2018 05:01:04 +0000 Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-ext4-owner@vger.kernel.org List-ID: https://bugzilla.kernel.org/show_bug.cgi?id=201685 --- Comment #79 from Hao Wei Tee (angelsl@in04.sg) --- (In reply to Néstor A. Marchesini from comment #78) > Well, guys, this seems to pass the test, after several reboots every several > hours of use, I had no more corruptions of my four partitions mdadm raid1. > The solution was to delete the ext4 folder from my kernel 4.19.5 and copy > the ext4 folder from my previous kernel 4.18.20 and recompiling the tree > 4.19.5. > > $ uname -a > Linux pc-user 4.19.5-gentoo #1 SMP PREEMPT Thu Nov 29 00:45:31 2018 x86_64 > AMD FX(tm)-8350 Eight-Core Processor AuthenticAMD GNU/Linux > > I was comparing both folders /fs/ext4 of the 4.18.20 and 4.19.5 trees with > meld and there are several modifications, unfortunately it exceeds my > knowledge. > At least on this side I affirm that the problem is gone, we will see it > happen with later patches. If this is the case, perhaps you could bisect fs/ext4 between tags v4.18 and v4.19? $ git bisect start v4.19 v4.18 -- fs/ext4 -- You are receiving this mail because: You are watching the assignee of the bug.