On Tuesday 14 May 2019, Arthur Marsh wrote: > Apologies, I had forgotten to > > got bisect - - hard origin/master > > I am still seeing the corruption leading to the invalid block error on 5.1.0+ > kernels on both my machines. > > Arthur.
I've been probably hit by the same bug. ext3 filesystem on my test machine was corrupted twice with 5.1.0+. Only the corruption was heavier. Some files that were open (e.g. logs) became cros-linked with files that were not used for ages. -- Ondrej Zary
