On Sun 17-02-19 00:29:40, Meelis Roos wrote: > > > The result of the bisection is > > > [88dbcbb3a4847f5e6dfeae952d3105497700c128] blkdev: avoid migration stalls for blkdev pages > > > > > > Is that result relevant for the problem or should I continue bisecting between 4.20.0 and the so far first bad commit? > > > > Can you try reverting the commit and see if it makes the problem go away? > > Tried reverting it on top of 5.0.0-rc6-00153-g5ded5871030e and it seems > to make the kernel work - emerge --sync succeeded. > > Unfinished further bisection has also not yielded any other bad revisions > so far. Hum, weird. I have hard time understanding how that change could be causing fs corruption on Aplha but OTOH it is not completely unthinkable. With this commit we may migrate some block device pages we were not able to migrate previously and that could be causing some unexpected issue. I'll look into this. Honza -- Jan Kara <jack@xxxxxxxx> SUSE Labs, CR
