From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 208325] f2fs inconsistent node block
Date: Wed, 01 Jul 2020 06:55:42 +0000 [thread overview]
Message-ID: <bug-208325-202145-nSN9Rs5k7N@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 #5 from Chao Yu (chao@kernel.org) ---
(In reply to zKqri0 from comment #4)
> >[print_node_info: 271] Node ID [0x203a7962:540703074] is direct node or
> >>indirect node.
> >[0] [0x5452202c : 1414668332]
> >[1] [0x45445f4d : 1162108749]
> >[2] [0x4444414c : 1145323852]
> >[3] [0x202c2952 : 539765074]
> >[4] [0x6e657665 : 1852143205]
> >[5] [0x6f687420 : 1869116448]
> >[6] [0x20686775 : 543713141]
> >[7] [0x69207469 : 1763734633]
> >[8] [0x6f6e2073 : 1869488243]
> >[9] [0x46202e74 : 1176514164]
> >[10] [0x69207869 : 1763735657]
> >Invalid (i)node block
I don't see any valid information from this, could you please upload the raw
block if possible?
--
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-07-01 6:55 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
2020-07-01 5:01 ` bugzilla-daemon
2020-07-01 6:55 ` bugzilla-daemon [this message]
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-nSN9Rs5k7N@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).