From: Artem Bityutskiy <dedekind1@gmail.com>
To: Anatolij Gustschin <agust@denx.de>
Cc: linux-mtd@lists.infradead.org, Detlev Zundel <dzu@denx.de>
Subject: Re: UBIFS recovery stops
Date: Tue, 22 Feb 2011 07:37:21 +0200 [thread overview]
Message-ID: <1298353041.20562.6.camel@koala> (raw)
In-Reply-To: <20110221165517.15e897ea@wker>
On Mon, 2011-02-21 at 16:55 +0100, Anatolij Gustschin wrote:
> The small corrupted data area in the flash seems to result
> from an uncompleted write operation: repeated reading from
> this area shows, that the bit values flip.
The first quick band-aid could be re-trying reading several times when
CRC error happens. This could improve things somewhat.
The proper solution is to make sure every LEB which could be being
written to at the power cut time gets erased on the next mount. Namely,
we need to do "atomic LEB change" for all journal heads when recovering.
Also, we need to be able to simulate unstable bits to efficiently test.
This is where I wanted to start from.
--
Best Regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2011-02-22 5:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 15:55 UBIFS recovery stops Anatolij Gustschin
2011-02-22 5:20 ` Artem Bityutskiy
2011-02-22 5:37 ` 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=1298353041.20562.6.camel@koala \
--to=dedekind1@gmail.com \
--cc=agust@denx.de \
--cc=dzu@denx.de \
--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