linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Matthieu CASTET <matthieu.castet@parrot.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: RE : UBI/UBIFS interrupted write page handling
Date: Mon, 18 Oct 2010 13:21:13 +0300	[thread overview]
Message-ID: <1287397273.1972.37.camel@localhost> (raw)
In-Reply-To: <4CA9D2A0.6010508@parrot.com>

On Mon, 2010-10-04 at 15:12 +0200, Matthieu CASTET wrote:
> Artem Bityutskiy a écrit :
> > On Tue, 2010-09-28 at 09:47 +0200, Matthieu CASTET wrote:
> >> Artem Bityutskiy a écrit :
> >>> On Sun, 2010-09-26 at 20:58 +0300, Artem Bityutskiy wrote:
> >>>
> >> That's better : interrupt erased page are not put anymore in corrupted list.
> >> But I have problem with interrupt write :
> >> this night the test crashed [1].
> > 
> > Yeah, this should be fixed by forcing LEB refresh for the last LEBs of
> > journal heads. This problem exists long time. I'll work on this and send
> > you patches.
> UBI will need also some patch.
> For example in case of wear leveling, ubi could move a leb from a peb to 
> another and the write can be interrupted.

Hmm, yeah, we have CRC in this case and we rely on CRC. However, if the
write to the last page was interrupted, it can be unstable and can
sometimes be read correctly, but sometimes incorrectly. So UBI should
refresh such PEBs.

I guess it is easier to start with UBI first.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

      reply	other threads:[~2010-10-18 10:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-09 13:15 UBI/UBIFS interrupted write page handling Matthieu CASTET
2010-09-09 17:51 ` Artem Bityutskiy
2010-09-20 18:14   ` Artem Bityutskiy
2010-09-23 16:14     ` Matthieu CASTET
2010-09-23 18:35       ` Artem Bityutskiy
     [not found]         ` <F5C24FC168F95048BB6B9E0B13EB33152BA6F5304E@DIAMANT.xi-lite.lan>
2010-09-26 17:58           ` RE : " Artem Bityutskiy
2010-09-28  6:58             ` Artem Bityutskiy
2010-09-28  7:47               ` Matthieu CASTET
2010-09-28  8:02                 ` Matthieu CASTET
2010-09-28  8:02                 ` Artem Bityutskiy
2010-09-28 16:06                   ` Matthieu CASTET
2010-09-28 18:34                     ` Artem Bityutskiy
2010-10-04 13:12                   ` Matthieu CASTET
2010-10-18 10:21                     ` Artem Bityutskiy [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=1287397273.1972.37.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=matthieu.castet@parrot.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;
as well as URLs for NNTP newsgroup(s).