From: Tastky <tastky@gmail.com>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [BUG] "kernel BUG at fs/f2fs/segment.c"
Date: Sat, 30 Nov 2013 18:59:53 +0100 [thread overview]
Message-ID: <529A2799.4050305@gmail.com> (raw)
In-Reply-To: <529A1FBC.2000603@gmail.com>
Alright, I'm able to mount it again with the disable_roll_forward
option. No other changes.
NB: There's a typo in the documentation at "disable_ext_identify": "so
f2fs does not aware"
On 30.11.2013 18:26, Tastky wrote:
> Now the bug already happens when merely mounting the partition.
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
prev parent reply other threads:[~2013-11-30 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-30 17:26 [BUG] "kernel BUG at fs/f2fs/segment.c" Tastky
2013-11-30 17:29 ` Tastky
2013-11-30 17:59 ` Tastky [this message]
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=529A2799.4050305@gmail.com \
--to=tastky@gmail.com \
--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).