FS#74906 - [linux] f2fs_gc oppupies 100% CPU

Attached to Project: Arch Linux
Opened by Guido Iodice (guiodic) - Monday, 30 May 2022, 11:33 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:13 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan Alexander Steffens (heftig)
David Runge (dvzrv)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

The problem started when I symlinked a file in my /home/user to a file in my /root (both partitions are f2fs).
By removing that symlink the problem seems no longer occurs.
From dmesg I don't see any error related to f2fs.

UUID=... / f2fs defaults,noatime,nodiscard 0 1
UUID=... /home f2fs defaults,noatime,nodiscard 0 2
This task depends upon

Closed by  Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:13 GMT
Reason for closing:  Moved
Additional comments about closing:  https://gitlab.archlinux.org/archlinux/p ackaging/packages/linux/issues/1
Comment by Guido Iodice (guiodic) - Monday, 30 May 2022, 11:53 GMT
I was too optimistic. The problem reoccurred.

217 root 20 0 0.0m 99.3 0.0 12:28.48 R f2fs_gc-259:3

the only related error I see the logs is:

30/05/22 13:13 kernel nvme nvme0: missing or invalid SUBNQN field.

I forced fsck on all partitions, but with no result.
Comment by Jack Gargasz (plague) - Monday, 30 May 2022, 23:40 GMT
Same. This begins a few days ago, and renders my system nonoperational...
In my case there are no symlinks.
Comment by Guido Iodice (guiodic) - Monday, 30 May 2022, 23:44 GMT
Maybe it is because some change in f2fs in linux kernel 5.18
I'm using 5.15 lts to test.
Comment by Guido Iodice (guiodic) - Monday, 30 May 2022, 23:45 GMT
my f2fs mounted partitions:

/dev/nvme0n1p3 on / type f2fs (rw,noatime,lazytime,background_gc=on,nodiscard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,alloc_mode=default,checkpoint_merge,fsync_mode=posix,discard_unit=block)
/dev/nvme0n1p4 on /home type f2fs (rw,noatime,lazytime,background_gc=on,nodiscard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,alloc_mode=default,checkpoint_merge,fsync_mode=posix,discard_unit=block)
/dev/nvme1n1 on /run/media/guido/nvme1 type f2fs (rw,noatime,lazytime,background_gc=on,nodiscard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,alloc_mode=default,checkpoint_merge,fsync_mode=posix,compress_algorithm=lz4,compress_log_size=2,compress_mode=fs,compress_cache,discard_unit=block)
Comment by Jack Gargasz (plague) - Tuesday, 31 May 2022, 00:34 GMT
Mine is on LVM (2xNVMe):

/dev/mapper/vg_ssd-lv_root on / type f2fs (rw,noatime,lazytime,background_gc=on,nodiscard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,alloc_mode=default,nocheckpoint_merge,fsync_mode=posix,discard_unit=block)

/dev/mapper/vg_ssd-lv_home on /home type f2fs (rw,noatime,lazytime,background_gc=on,nodiscard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,alloc_mode=default,nocheckpoint_merge,fsync_mode=posix,discard_unit=block)

/dev/mapper/vg_ssd2-lv_backup on /mnt/backup type f2fs (rw,noatime,lazytime,background_gc=on,nodiscard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,alloc_mode=default,checkpoint_merge,fsync_mode=posix,discard_unit=block)
Comment by loqs (loqs) - Tuesday, 31 May 2022, 14:54 GMT
Could be https://bugzilla.kernel.org/show_bug.cgi?id=215935 can you produce the same backtrace if you build the kernel linked in the report?
Also for reference your upstream bug report https://bugzilla.kernel.org/show_bug.cgi?id=216050
Comment by Guido Iodice (guiodic) - Tuesday, 31 May 2022, 16:14 GMT
@loqs

I think is a different bug. I have no errors in logs
Comment by Guido Iodice (guiodic) - Tuesday, 31 May 2022, 18:18 GMT
@plague: could you please add the comment here? https://bugzilla.kernel.org/show_bug.cgi?id=216050
Comment by Toolybird (Toolybird) - Saturday, 30 July 2022, 02:09 GMT
There appears to be progress in the linked upstream report, though no resolution yet. Please let us know if/when a fix becomes available.

Dupe  FS#75144 

Loading...