From: Jan Altenberg <jan@linutronix.de>
To: jaegeuk.kim@samsung.com
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: BUG_ON in recovery.c after powercut
Date: Wed, 16 Oct 2013 10:51:27 +0200 [thread overview]
Message-ID: <1381913487.2431.17.camel@bender.lan> (raw)
In-Reply-To: <1381812859.992.26.camel@kjgkr>
Hi,
thanks a lot for the feedback.
> If possible, can you test the below scenario with the latest f2fs?
I will see, what I can do. I'll need to merge a couple of patches to get
the eMMC stuff working. I'll check that ASAP, but I'm afraid, I can't do
this, before I leave vor LCE and ELCE.
> The latest f2fs is available from:
> http://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs.git/log/?h=dev
>
> Otherwise, could you send the broken image to me?
For sure, but the image is pretty big (round about 1 gig). But I can put
it on our web machine (just let me know).
Unfortunately, I was just able to trigger that issue with that full
blown Angstrom image.
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 8:51 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 [this message]
2013-10-16 16:20 ` Jarkko Lavinen
2013-10-16 20:47 ` Jan Altenberg
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=1381913487.2431.17.camel@bender.lan \
--to=jan@linutronix.de \
--cc=jaegeuk.kim@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).