https://bugzilla.kernel.org/show_bug.cgi?id=208325
--- Comment #2 from zkq...@gmail.com --- (In reply to Chao Yu from comment #1) > Hi, thanks for the report. > > What's you mkfs/mount option? > > I've no idea whether this is a f2fs bug or not, as you said device can be > trusted, so almostly it should be a software bug. > > One case I can image could be that apps bypassing filesystem to write data > via LBA directly, then data can be corrupted. > > If possible, could you please help to add below three patches to recompile > the kernel > > https://lore.kernel.org/linux-f2fs-devel/20200628122940.29665-1- > yuch...@huawei.com/T/#t > > [f2fs-dev] [PATCH 1/3] f2fs: fix wrong return value of f2fs_bmap_compress() > [f2fs-dev] [PATCH 2/3] f2fs: support to trace f2fs_bmap() > [f2fs-dev] [PATCH 3/3] f2fs: support to trace f2fs_fiemap() > > Then, use below commands to see whether there is apps are lookuping LBA: > > echo 1 > /sys/kernel/debug/tracing/events/f2fs/f2fs_bmap/enable > echo 1 > /sys/kernel/debug/tracing/events/f2fs/f2fs_fiemap/enable > cat /sys/kernel/debug/tracing/trace_pipe |grep f2fs Mount options are "/dev/sda2 on / type f2fs (rw,relatime,lazytime,background_gc=on,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,alloc_mode=default,fsync_mode=posix)". I patched my laptop's kernel with those patches but I don't see anything in "trace_pipe" while I'm getting invalid argument errors. Also I noticed that the "nid" and "node_footer" are the same always in the error so its only one node block that's messed up. Maybe a raw copy of that node block will help find what caused it ? -- 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
