Linux-f2fs-devel Archive on
 help / color / Atom feed
Subject: [f2fs-dev] [Bug 208325] f2fs inconsistent node block
Date: Mon, 29 Jun 2020 06:17:37 +0000
Message-ID: <> (raw)
In-Reply-To: <>

--- Comment #2 from ---
(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
> [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

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

  parent reply index

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-26 10:22 [f2fs-dev] [Bug 208325] New: " bugzilla-daemon
2020-06-28 12:44 ` [f2fs-dev] [Bug 208325] " bugzilla-daemon
2020-06-29  6:17 ` bugzilla-daemon [this message]
2020-06-30 14:08 ` bugzilla-daemon
2020-07-01  5:01 ` bugzilla-daemon
2020-07-01  6:55 ` bugzilla-daemon
2020-07-05  7:40 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-f2fs-devel Archive on

Archives are clonable:
	git clone --mirror linux-f2fs-devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-f2fs-devel linux-f2fs-devel/ \
	public-inbox-index linux-f2fs-devel

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone