Skip to main content ↑ ↓
Topic: f2fs_gc 8:1 EATS 100% CPU Locking Computer Out of Usage (Read 352 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

f2fs_gc 8:1 EATS 100% CPU Locking Computer Out of Usage

Very serious. The following process:

f2fs_gc 8:1

locks my computer totally, when I leave it running overnight. "/" is on ext4 and "/home" is on f2fs. Never had this problem, ever (2-3 years). The reason for this is that GRUB probably would not work properly (or would stop doing its job correctly) if "/" was f2fs. Just like its doing now  (heard something) if I had  "/" as xfs. So that was precaucion on my part.

Some links:
https://bugzilla.kernel.org/show_bug.cgi?id=216050
https://bugs.archlinux.org/task/74906
https://www.linux.org.ru/forum/general/16779499 (russian site, must be highly linked/popular if it pops up high at the top...)


Re: f2fs_gc 8:1 EATS 100% CPU Locking Computer Out of Usage

Reply #1 –
The answer, if you have the same issue which seems likely, seems to be in the ongoing bug report you posted.

Either patch and compile your own kernel.
Try older lts kernels.
Or use a different filesystem.

Edit: I've had a bit more of a scan through that bug report and my suggestion, if the data in /home is important to you, and especially if you don't have it backed up in its entirety on another filesystem, would be use a different filesystem.

Re: f2fs_gc 8:1 EATS 100% CPU Locking Computer Out of Usage

Reply #2 –

 Sometimes it gets stuck on higher cpu. Happened to me only once in ~3 years. I've just rebooted and everything went back to normal.
 
 I have my root on f2fs also and I've heard we can even have the /boot on f2fs. Make sure you fsck when you get sudden power loss/crashes and defrag once in  while. Best file system in my opinion.

 The only no go is to downgrade the kernel bellow that f2f version that was used to create your partitions when you installed your system.

Re: f2fs_gc 8:1 EATS 100% CPU Locking Computer Out of Usage

Reply #3 –
Kernels are not fully compatible with f2fs. F2fs MUST report to kernel any fault, but it cannot see anything. So instead of relying of internals of f2fs one must force scan/repair from external boot (with force parameters to repair). It happens regardless of where the "fault" is. In my case "/" is ext4 and /home is f2fs. One MUST scan f2fs with force.