From: Jan Altenberg <jan@linutronix.de>
To: Jarkko Lavinen <j.lavinen@samsung.com>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: BUG_ON in recovery.c after powercut
Date: Wed, 16 Oct 2013 22:47:43 +0200 [thread overview]
Message-ID: <1381956463.3106.8.camel@moestavern> (raw)
In-Reply-To: <20131016162043.GA10000@wsf-1107.seri.co.uk>
On Wed, 2013-10-16 at 19:20 +0300, Jarkko Lavinen wrote:
> > If possible, can you test the below scenario with the latest f2fs?
>
> I would be also interested in studying such image, so could you
> please send it to me also?
Ok, no problem at all. As already mentioned, I can put it on our
webmachine. But the image is about 1 gig.
If one of you guys is planning to attend LCE or ELCE in Edinburgh, just
let me know! I can take that board with me!
I'm not sure if I can work on this topic before I leave for LCE, but I
will continue testing and upload the image when I'm back to the office.
> I am concerned or curious about F2FS tolerance against power
> cuts.
>
> In my previous life at Nokia we did once power cut testing for
> ext3 and ext4 file systems on eMMC. There was an AC switch which
> cut the power off at random times. Ext3 didn't survive the test,
> ext4 did.
That's what we did with F2FS. That triggered the issue described in my
previous mail.
Cheers,
Jan
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
next prev parent reply other threads:[~2013-10-16 20:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 14:23 BUG_ON in recovery.c after powercut Jan Altenberg
2013-10-15 4:54 ` Jaegeuk Kim
2013-10-16 8:51 ` Jan Altenberg
2013-10-16 16:20 ` Jarkko Lavinen
2013-10-16 20:47 ` Jan Altenberg [this message]
2013-10-17 18:25 ` Jan Altenberg
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=1381956463.3106.8.camel@moestavern \
--to=jan@linutronix.de \
--cc=j.lavinen@samsung.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).