public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS recovery fails
Date: Thu, 20 Oct 2011 19:36:19 +0300	[thread overview]
Message-ID: <1319128586.20953.19.camel@sauron> (raw)
In-Reply-To: <Pine.LNX.4.64.1110181007100.30940@lnxricardw.se.axis.com>

[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]

On Tue, 2011-10-18 at 10:11 +0200, Ricard Wanderlof wrote:
> On Mon, 17 Oct 2011, Artem Bityutskiy wrote:
> 
> > [...] Unfortunately, no one really invested time into making UBIFS 
> > support MLC very well. It needs some more work. It also have some issues 
> > related to unstable bits in modern SLC.
> >
> > In short - if you want to use UBIFS on MLC - you should not have unclean
> > reboots. If you want to make UBIFS 100% uclean-reboot save on MLC - you
> > need to work on it some more.
> >
> > We (the original authors) developed and tested it on very robust SLC
> > NAND.
> 
> Do you have any specifics on what the issues are with MLC ?

Yeah, described at the web site, please send patches if you have
something to add!

> Since UBI implements bit scrubbing and eraseblock torture on questionable 
> blocks it would seem that a lot of the work has been done in order to 
> handle unstable bits. Is there some issue which is related specifically to 
> bit flips happening while the system is powered off?

The definition of unstable bits in MTD community is probably not what
you though of. I've added the docs at the web site as well :-)

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  parent reply	other threads:[~2011-10-20 16:36 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 [this message]
2011-10-18  8:29   ` Ivan Djelic
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=1319128586.20953.19.camel@sauron \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=ricard.wanderlof@axis.com \
    /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