From: Ivan Djelic <ivan.djelic@parrot.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Daniel Kuhn <cheeef@swissonline.ch>
Subject: Re: UBIFS recovery fails
Date: Tue, 18 Oct 2011 10:29:55 +0200 [thread overview]
Message-ID: <20111018082955.GB5997@parrot.com> (raw)
In-Reply-To: <1318882668.2172.10.camel@koala>
On Mon, Oct 17, 2011 at 09:17:48PM +0100, Artem Bityutskiy wrote:
>
> If someone wants to see UBIFS 100% or near 100% power-cut safe on
> MLC or one of shitty modern SLCs - he needs to invest men-hours.
> I can help by suggesting and reviewing. Although the funny thing is
> that eMMCs die and lose data in case of power cuts very often :-)
Hi Artem,
That's interesting... Do you have more details or any data on those eMMC
power-cut failures ?
I plan to be working soon (December) on UBIFS robustness issues with unstable
modern SLCs; besides using nandsim to simulate SLC (and maybe MLC) issues,
I also have real hardware with a power-cutting framework ready for testing.
Best Regards,
--
Ivan
next prev parent reply other threads:[~2011-10-18 8:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 13:29 UBIFS recovery fails Daniel Kuhn
2011-10-17 20:17 ` Artem Bityutskiy
2011-10-18 8:11 ` Ricard Wanderlof
2011-10-18 8:42 ` Ivan Djelic
2011-10-20 16:37 ` Artem Bityutskiy
2011-10-20 16:36 ` Artem Bityutskiy
2011-10-18 8:29 ` Ivan Djelic [this message]
2011-10-19 15:15 ` Artem Bityutskiy
2011-10-19 17:27 ` Ivan Djelic
2011-10-18 12:47 ` Jean-Sébastien Gagnon
2011-10-18 14:54 ` Ivan Djelic
2011-10-18 15:10 ` Jean-Sébastien Gagnon
2011-10-18 15:32 ` Ivan Djelic
2011-10-18 16:05 ` Jean-Sébastien Gagnon
2011-10-19 6:50 ` Ricard Wanderlof
2011-10-19 10:22 ` Ivan Djelic
2011-10-19 12:17 ` Atlant Schmidt
2011-10-19 12:52 ` Ricard Wanderlof
2011-10-19 13:30 ` Atlant Schmidt
2011-10-20 16:43 ` Artem Bityutskiy
2011-10-24 7:00 ` Ricard Wanderlof
2011-10-29 19:43 ` Artem Bityutskiy
2011-10-20 14:14 ` Artem Bityutskiy
2011-10-18 15:29 ` Daniel Kuhn
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=20111018082955.GB5997@parrot.com \
--to=ivan.djelic@parrot.com \
--cc=cheeef@swissonline.ch \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
/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).