From: Vitaly Wool <vwool@ru.mvista.com>
To: Russ Dill <russ.dill@gmail.com>
Cc: Linux-MTD Mailing List <linux-mtd@lists.infradead.org>,
Josh Boyer <jwboyer@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [RFC] read-only filesystem support for NAND flash devices
Date: Fri, 12 May 2006 12:55:21 +0400 [thread overview]
Message-ID: <44644D79.7000903@ru.mvista.com> (raw)
In-Reply-To: <f9d2a5e10605111626u743b101dgfc7e90422dec9a80@mail.gmail.com>
Russ Dill wrote:
> True, I also realized another possible shortcut. If a blocks gets an
> ECC correction on a read, rewrite it to a free block, erase the block,
> rewrite it from the data written to the free block, and then erase the
> free block. You'd need to put some info in the OOB so you could know
> what the state is on power recovery.
>
Oh thanks, that's the idea I'm going to use. It's a pretty reasonable
assumption that 1 byte out of OOB is available as there's not going to
be anything in OOB but ECC code in case of RO filesystem.
Vitaly
next prev parent reply other threads:[~2006-05-12 8:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 9:52 [RFC] read-only filesystem support for NAND flash devices Vitaly Wool
2006-05-10 11:00 ` Josh Boyer
2006-05-10 11:20 ` Vitaly Wool
2006-05-10 13:39 ` Jörn Engel
2006-05-10 20:11 ` Josh Boyer
2006-05-11 19:06 ` Russ Dill
2006-05-11 22:26 ` David Woodhouse
2006-05-11 23:26 ` Russ Dill
2006-05-11 23:34 ` Josh Boyer
2006-05-11 23:58 ` Russ Dill
2006-05-12 8:55 ` Vitaly Wool [this message]
2006-05-12 8:52 ` Vitaly Wool
2006-05-13 14:08 ` David Woodhouse
2006-05-10 17:04 ` Atsushi Nemoto
2006-05-10 17:20 ` Josh Boyer
2006-05-10 20:01 ` Jörn Engel
2006-05-11 14:23 ` Atsushi Nemoto
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=44644D79.7000903@ru.mvista.com \
--to=vwool@ru.mvista.com \
--cc=dwmw2@infradead.org \
--cc=jwboyer@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=russ.dill@gmail.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