From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 206551] Failed to initialize F2FS segment manager (-117)
Date: Mon, 17 Feb 2020 07:17:44 +0000 [thread overview]
Message-ID: <bug-206551-202145-wQuRx3h4aJ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206551-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206551
Chao Yu (chao@kernel.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |chao@kernel.org
--- Comment #2 from Chao Yu (chao@kernel.org) ---
Both kernel log“Mismatch valid blocks” and fsck log "SIT bitmap is 0" says SIT
table may be inconsistent in your image.
I noticed that you're using a swap partition, may I ask where did you build the
swap partition? in your f2fs image? What's your swap option?
Quoted: "I use hibernation to a swap partition"
--
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-02-17 7:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 19:14 [f2fs-dev] [Bug 206551] New: Failed to initialize F2FS segment manager (-117) bugzilla-daemon
2020-02-16 19:15 ` [f2fs-dev] [Bug 206551] " bugzilla-daemon
2020-02-17 7:17 ` bugzilla-daemon [this message]
2020-02-17 9:26 ` bugzilla-daemon
2020-02-18 1:32 ` bugzilla-daemon
2020-02-18 7:19 ` bugzilla-daemon
2020-02-20 7:03 ` 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-206551-202145-wQuRx3h4aJ@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).