https://bugzilla.kernel.org/show_bug.cgi?id=216050
--- Comment #16 from Chao Yu (c...@kernel.org) --- (In reply to Jaegeuk Kim from comment #14) > Re #9, > > Thank you so much. > > f2fs_gc-254:2-1156 [013] ..... 22290.243361: > f2fs_lookup_extent_tree_end: dev = (254,2), ino = 1409621, pgofs = 234, > ext_info(fofs: 0, blk: 0, len: 0) > f2fs_gc-254:2-1156 [013] ..... 22290.243362: > f2fs_lookup_extent_tree_start: dev = (254,2), ino = 1409621, pgofs = 234 > f2fs_gc-254:2-1156 [013] ..... 22290.243362: > f2fs_lookup_extent_tree_end: dev = (254,2), ino = 1409621, pgofs = 234, > ext_info(fofs: 0, blk: 0, len: 0) > f2fs_gc-254:2-1156 [013] ..... 22290.243362: > f2fs_lookup_extent_tree_start: dev = (254,2), ino = 1409621, pgofs = 234 > f2fs_gc-254:2-1156 [013] ..... 22290.243362: > f2fs_lookup_extent_tree_end: dev = (254,2), ino = 1409621, pgofs = 234, > ext_info(fofs: 0, blk: 0, len: 0) > f2fs_gc-254:2-1156 [013] ..... 22290.243362: > f2fs_lookup_extent_tree_start: dev = (254,2), ino = 1409621, pgofs = 234 > f2fs_gc-254:2-1156 [013] ..... 22290.243362: > f2fs_lookup_extent_tree_end: dev = (254,2), ino = 1409621, pgofs = 234, > ext_info(fofs: 0, blk: 0, len: 0) > f2fs_gc-254:2-1156 [013] ..... 22290.243362: > f2fs_lookup_extent_tree_start: dev = (254,2), ino = 1409621, pgofs = 234 > > > It seems this disk is dm-2, since the extent hit count is something below. > - Hit Ratio: 0% (38193 / 78044163449) > > I'm suspecting this flow, but not sure where it goes into a loop. > > f2fs_gc > -> gc_data_segment > -> f2fs_get_read_data_page > -> f2fs_lookup_extent_cache I suspect this path, it looks impossible though... - move_data_page - f2fs_get_lock_data_page - f2fs_get_read_data_page -- 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
