https://bugzilla.kernel.org/show_bug.cgi?id=216050
--- Comment #180 from kelak (ale...@gmx.net) --- (In reply to Guido from comment #179) > (In reply to kelak from comment #178) > > >Jaegeuk has proposed a workaround solution as below, it aims to enable > from > > >6.6-rc1, could you please have a try with it? > > > > > > > > >https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/commit/?h=dev&id=5a47ad28e6061c8fddf5c82d49fdc3280a80b2c4 > > > > > > I'll try to build and test a 6.4.x kernel next week which has that > > workaround-patch included. > > Did it work? I have rebuilt the arch linux kernel 6.4.6 with the mentioned patch last weekend. I have an uptime of one week now, and the issue has not occurred yet. So it's too short to say anything definite. However, before I started the patched kernel I played around with the garbage-collect-script. I observed that After some iterations the f2fs_gc-thread took ~25-30% CPU and the number of dirty-segments stayed constant at around 10000. I stopped the garbage-collect-script, but f2fs-gc-thread CPU usage stayed at ~20-30%. I rebooted after ~15 minutes. I observed this for both kernels, the patched one and the unpatched one. I'll leave the patched kernel running for some more weeks. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
