From: "Jörn Engel" <joern@logfs.org>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: Linux mtd <linux-mtd@lists.infradead.org>
Subject: Re: Some news for this: [PATCH] [MTD] BLOCK_RO: Readonly Block Device Layer Over MTD ?
Date: Thu, 22 Nov 2007 14:26:50 +0100 [thread overview]
Message-ID: <20071122132650.GA27525@lazybastard.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0711220858190.523@lnxricardw.se.axis.com>
On Thu, 22 November 2007 08:58:58 +0100, Ricard Wanderlof wrote:
> On Wed, 21 Nov 2007, Jörn Engel wrote:
>
> >> If data is corrupted between tow read even journalized are log file
> >> system will loose data.
> >> Either there is a mechanism I missed in this file system or 2 bits
> >> flipped are so rare that this event can be ignored.
> >
> > It means that NAND needs scrubbing.
>
> By 'scrubbing' do you mean erasing the blocks in question and rewriting
> them with the same data in order to put fresh data back in the bit cells?
Please don't reply to the list only. If you are asking me a question,
it is really impolite to send it elsewhere. And I bet others would like
to stay on Cc: as well.
http://en.wikipedia.org/wiki/Memory_scrubbing
Trivial scrubbing could leave the block in an erased or
partially-written state if power-loss occurs at an inconvenient time.
So scrubbing should be performed in some higher layer like an FTL, a
filesystem, system maintenance applications, etc.
Jörn
--
Science is like sex: sometimes something useful comes out,
but that is not the reason we are doing it.
-- Richard Feynman
next prev parent reply other threads:[~2007-11-22 14:05 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 14:27 Some news for this: [PATCH] [MTD] BLOCK_RO: Readonly Block Device Layer Over MTD ? Gregory CLEMENT
2007-11-21 16:08 ` Jörn Engel
2007-11-21 16:28 ` Gregory CLEMENT
2007-11-21 16:58 ` Josh Boyer
2007-11-21 17:07 ` Gregory CLEMENT
2007-11-21 17:13 ` Josh Boyer
2007-11-21 17:15 ` Jörn Engel
2007-11-21 17:32 ` Gregory CLEMENT
2007-11-21 17:43 ` Vitaly Wool
2007-11-21 17:45 ` Jörn Engel
2007-11-21 17:56 ` Vitaly Wool
2007-11-21 18:04 ` Jörn Engel
2007-11-23 14:35 ` Gregory CLEMENT
2007-11-23 14:45 ` Jörn Engel
2007-11-23 15:06 ` Gregory CLEMENT
2007-11-21 20:46 ` Ricard Wanderlof
2007-11-21 21:32 ` Jörn Engel
2007-11-21 22:33 ` Gregory CLEMENT
2007-11-21 22:54 ` Jörn Engel
2007-11-22 7:58 ` Ricard Wanderlof
2007-11-22 13:26 ` Jörn Engel [this message]
2007-11-23 7:42 ` Ricard Wanderlof
2007-11-23 8:18 ` Artem Bityutskiy
2007-11-23 9:08 ` Ricard Wanderlof
2007-11-23 9:21 ` Artem Bityutskiy
2007-11-23 9:28 ` Ricard Wanderlof
2007-11-23 18:40 ` David Brown
2007-11-26 9:42 ` Ricard Wanderlof
2007-11-26 13:58 ` Claudio Lanconelli
2007-11-23 8:19 ` Artem Bityutskiy
2007-11-23 12:46 ` Jörn Engel
2007-11-22 7:58 ` Ricard Wanderlof
2007-11-22 13:08 ` Jamie Lokier
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=20071122132650.GA27525@lazybastard.org \
--to=joern@logfs.org \
--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