From: Matthieu CASTET <matthieu.castet@parrot.com>
To: "dedekind1@gmail.com" <dedekind1@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: RE : UBI/UBIFS interrupted write page handling
Date: Mon, 4 Oct 2010 15:12:00 +0200 [thread overview]
Message-ID: <4CA9D2A0.6010508@parrot.com> (raw)
In-Reply-To: <1285660934.2437.44.camel@localhost>
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.
>
> We also have the outstanding gc_lnum problem - did you see it in new
> ubifs?
No, I find the cause of that. I was missing a patch in my backport tree.
Matthieu
next prev parent reply other threads:[~2010-10-04 13:12 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 [this message]
2010-10-18 10:21 ` Artem Bityutskiy
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=4CA9D2A0.6010508@parrot.com \
--to=matthieu.castet@parrot.com \
--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).