From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 208325] f2fs inconsistent node block
Date: Tue, 30 Jun 2020 14:08:37 +0000 [thread overview]
Message-ID: <bug-208325-202145-t9Slikzq2V@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208325-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=208325
--- Comment #3 from Chao Yu (chao@kernel.org) ---
(In reply to zKqri0 from comment #2)
> 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)".
It looks it's default mount options.
Did you use any special mkfs options? like -O [feature_name]?
>
> 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 ?
Yes, please, I can parse it with dentry_block, inode or dnode structure to see
what it looks like, and what kind of fields are corrupted.
--
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 prev parent reply other threads:[~2020-06-30 14:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 10:22 [f2fs-dev] [Bug 208325] New: f2fs inconsistent node block bugzilla-daemon
2020-06-28 12:44 ` [f2fs-dev] [Bug 208325] " bugzilla-daemon
2020-06-29 6:17 ` bugzilla-daemon
2020-06-30 14:08 ` bugzilla-daemon [this message]
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-t9Slikzq2V@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.