From: Philippe De Muyter <phdm@macq.eu>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: f2fs_bug_on in init_dirty_segmap
Date: Wed, 8 Mar 2017 15:24:32 +0100 [thread overview]
Message-ID: <20170308142432.GA31333@frolo.macqel> (raw)
Hi f2fs developpers,
Please excuse my maybe dumb question.
I recently encountered a kernel panic at root mount time (thus making my
system unusable, as my root partition is formatted as f2fs) due to the
following segment in fs/f2fs/segment.c:init_dirty_segmap
if (valid_blocks > sbi->blocks_per_seg) {
f2fs_bug_on(sbi, 1); <<<<<<<<<<<<<<<<<<<<
continue;
}
Is that really a condition requiring a kernel panic, or could a read-only
mount be allowed ?
Philippe
--
Philippe De Muyter +32 2 6101532 Macq SA rue de l'Aeronef 2 B-1140 Bruxelles
------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
next reply other threads:[~2017-03-08 14:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 14:24 Philippe De Muyter [this message]
2017-03-08 21:52 ` f2fs_bug_on in init_dirty_segmap Jaegeuk Kim
2017-03-09 8:42 ` Philippe De Muyter
2017-03-09 23:11 ` Jaegeuk Kim
2017-03-10 9:28 ` Philippe De Muyter
2017-03-10 18:20 ` Jaegeuk Kim
2017-03-10 18:58 ` Philippe De Muyter
2017-03-11 21:01 ` Jaegeuk Kim
2017-03-12 10:32 ` Philippe De Muyter
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=20170308142432.GA31333@frolo.macqel \
--to=phdm@macq.eu \
--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).