From: bugzilla-daemon@kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 216669] New: f2fs inconsistent node block when executing f2fs_fill_super
Date: Mon, 07 Nov 2022 03:47:57 +0000 [thread overview]
Message-ID: <bug-216669-202145@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216669
Bug ID: 216669
Summary: f2fs inconsistent node block when executing
f2fs_fill_super
Product: File System
Version: 2.5
Kernel Version: 5.10
Hardware: ARM
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: f2fs
Assignee: filesystem_f2fs@kernel-bugs.kernel.org
Reporter: wang_wen@outlook.com
Regression: No
Our android phone could not fota/UL because the data partition can not mount
successfully. Checked the device's log and there were a bunch of errors like
"F2FS-fs (dm-51): inconsistent node block, nid:6, node_footer[nid:1053192010,
ino:2820544544,ofs:50883304,cpver:16464726221085140693,blkaddr:3937177732]"
during executing f2fs_fill_super function.
After the phone device rebooted requested by 'UpdateLauncher', it will get
into recovery mode with above error message(f2fs inconsistent node block). When
select "try again" item , this phone device still get into recovery mode
again.After try some times, the image of phone will rollback to previous image
version , the phone can boot up into home UI successfully.
This issue probably not caused by ufs failure as the phone can boot up
successfully with old image version. And, this issue does not occur on all
phone devices.
--
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
reply other threads:[~2022-11-07 3:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-216669-202145@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).