From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 208325] New: f2fs inconsistent node block
Date: Fri, 26 Jun 2020 10:22:46 +0000 [thread overview]
Message-ID: <bug-208325-202145@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=208325
Bug ID: 208325
Summary: f2fs inconsistent node block
Product: File System
Version: 2.5
Kernel Version: 5.7.2-arch1-1
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: f2fs
Assignee: filesystem_f2fs@kernel-bugs.kernel.org
Reporter: zKqri0@gmail.com
Regression: No
i was working with an android kernel tree and once when i was trying to build i
started getting errors like "make[1]: stat: drivers/input/touchscreen/Kconfig:
Invalid argument". checked my laptop's dmesg and there were a bunch of errors
like "F2FS-fs (sda2): inconsistent node block, nid:1761978,
node_footer[nid:540703074,ino:1937074503,ofs:212733452,cpver:7020105085017473824,blkaddr:1008758642]".
rebooted and the problem is still there whenever i try to build that kernel
tree. probably could just delete and clone it again but i kept it in case
having it will help with finding what caused this bug. its probably not caused
by ssd failure as i didnt get any sata errors and ive never got files corrupted
before and after this happened.
--
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
next reply other threads:[~2020-06-26 10:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 10:22 bugzilla-daemon [this message]
2020-06-28 12:44 ` [f2fs-dev] [Bug 208325] f2fs inconsistent node block bugzilla-daemon
2020-06-29 6:17 ` bugzilla-daemon
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:
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-208325-202145@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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).