From: Simon Haynes <simon@baydel.com>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: Bad Blocks On JFFS2/NAND
Date: Tue, 19 Oct 2004 15:39:36 +0100 [thread overview]
Message-ID: <E0CCB8742B31@baydel.com> (raw)
In-Reply-To: <1098186608.12223.857.camel@thomas>
Thomas,
I am using the ready pin.
On Tuesday 19 Oct 2004 12:50 pm, Thomas Gleixner wrote:
> On Tue, 2004-10-19 at 13:22, Simon Haynes wrote:
> > I have experienced a problem in which a JFF2 filesystem on NAND became
> > full. This is a root file system and constant writes to a logfile filled
> > the filesystem. On investigation it was found that the NAND device now
> > had hundreds of bad blocks.
> >
> > I started to investigate this and found that JFFS2 was announcing
> >
> > Newly-erased block contained word 0x1985e002 at offset 0x020f7e00
> >
> > Messages which result in my mtd/jffs2 code marking the block bad. What I
> > find strange is that a subsequent scan list the new block at a different
> > 16k offset when the device erasesize is 16k, in this case 0x020f0000. Is
> > that because my device is 128Mb and JFFS2 is using this 'virtual erase
> > size' of 32k ?
>
> Yes. The bad block code scans/marks physical blocks and JFFS2 operates
> on virtual ones, if the device size is big enough.
>
> > I have observed this now on several different NAND devices and it seems
> > to be more prominent while performing small writes.
> >
> > I am currently trying to work out if the erase is not completing, or this
> > is the wrong block or something else.
>
> Hmm, are you using Ready/Busy Pin or the timeout ?
>
> tglx
>
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2004-10-19 14:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 11:22 Bad Blocks On JFFS2/NAND Simon Haynes
2004-10-19 11:50 ` Thomas Gleixner
2004-10-19 14:39 ` Simon Haynes [this message]
2004-10-19 15:02 ` Thomas Gleixner
2004-10-19 15:18 ` Simon Haynes
2004-10-19 21:45 ` Michael Moedt
2004-10-19 21:55 ` Thomas Gleixner
2004-10-20 9:40 ` Simon Haynes
2004-10-20 9:53 ` Thomas Gleixner
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=E0CCB8742B31@baydel.com \
--to=simon@baydel.com \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
/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