From: Thomas Gleixner <tglx@linutronix.de>
To: Josh Boyer <jdub@us.ibm.com>
Cc: Vahid Fereydunkolahi <fereydunk@yahoo.com>,
linux-mtd@lists.infradead.org
Subject: Re: two questions about jffs2
Date: Wed, 11 May 2005 21:51:22 +0000 [thread overview]
Message-ID: <1115848282.22180.115.camel@tglx> (raw)
In-Reply-To: <1115239415.6079.3.camel@ibm-ptfdj7idx47.rchland.ibm.com>
On Wed, 2005-05-04 at 15:43 -0500, Josh Boyer wrote:
> JFFS2 handles bad blocks. It does this by detecting a block is bad, and
> then never doing anything with said block. The definition of a bad
> block is that it is marked as such in the spare area at manufacturing
> time. Any write/erase operation to such a block would cause this
> information to be lost. Therefore, JFFS2 does not touch these blocks
> during runtime.
Even if the filesystem misbehaves the nand driver in the mtd layer
refuses to write/erase bad blocks.
tglx
next prev parent reply other threads:[~2005-05-11 21:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 20:18 two questions about jffs2 Vahid Fereydunkolahi
2005-05-04 20:43 ` Josh Boyer
2005-05-11 21:51 ` Thomas Gleixner [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-04 19:07 Michael
2005-05-04 17:32 Vahid Fereydunkolahi
2005-05-04 0:15 Vahid Fereydunkolahi
2005-05-04 8:39 ` Artem B. Bityuckiy
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=1115848282.22180.115.camel@tglx \
--to=tglx@linutronix.de \
--cc=fereydunk@yahoo.com \
--cc=jdub@us.ibm.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