From: "" <simon@baydel.com>
To: MTD mailing list <linux-mtd@lists.infradead.org>
Cc: tglx@linutronix.de
Subject: Re: JFFS2 and bad blocks
Date: Mon, 6 Jan 2003 17:04:15 -0000 [thread overview]
Message-ID: <3E19B70F.1851.32F407@localhost> (raw)
In-Reply-To: <200212031403.42061.tglx@linutronix.de>
I download the CVS stuff mid December and again today. The
hardware ran ok before and could use jffs2 without errors but as I
added files it was slow and I could not make file systems on
partitions which contained bad blocks.
The new CVS code seems to be much quicker and I can erase,
mount and copy files to my new filesystem without error. I have set
up the specific driver to do soft ecc. I noticed that when I reboot the
system and the filesystem gets mounted I get errors. The more
writes that occur the more errors I seem to get. I ran a test for a
week or so over the break which generated log files. A reboot after
this produced thousands of errors but the filesystem seemed ok.
The errors are something like
Empty flash at 0x00469ffcb ends at 0x0046a000
or
jffs2_scan_dirent_node(): Node CRC failed on node at 0x0046a7f0
read 0xffffffff calculated 0xdec8161b
I was wondering if any of you could shed any light on this.
On 3 Dec 2002, at 14:03, Thomas Gleixner wrote:
> On Tuesday 03 December 2002 11:23, simon@baydel.com wrote:
> > I am using an SMC via the MTD layer. On one of the partitions I
> > would like to put a JFFS2 filesystem. Normally I erase the partition
> > and then mount it JFFS2. The problem is that if the partition has a
> > bad block I cannot erase or mount it. Does the bad block handling
> > have to be in the vendor specific nand driver ?
>
> Please use latest MTD-CVS code.
> Read http://www.linux-mtd.infradead.org/tech/nand.html
>
> --
> Thomas
> ____________________________________________________
> linutronix - competence in embedded & realtime linux
> http://www.linutronix.de
> mail: tglx@linutronix.de
__________________________
Simon Haynes - Baydel
Phone : 44 (0) 1372 378811
Email : simon@baydel.com
__________________________
next prev parent reply other threads:[~2003-01-06 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 10:23 JFFS2 and bad blocks simon
2002-12-03 13:03 ` Thomas Gleixner
2003-01-06 17:04 ` simon [this message]
2003-01-06 18:59 ` 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=3E19B70F.1851.32F407@localhost \
--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