https://bugzilla.kernel.org/show_bug.cgi?id=201685 --- Comment #80 from Rainer Fiebig (jrf@xxxxxxxxxxx) --- (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 you can bisect it as suggested in comment 79, please mind what Ted Tso has said in comment 69, para. 2. So, after you have hit a bad kernel, make sure that your fs is OK and do the next step (compiling) with a known-as-good-kernel (4.18.20). Otherwise you might get false negatives (wrong bads). -- You are receiving this mail because: You are watching the assignee of the bug.
