From: "Bernd Büttner" <b.buettner@mkc-gmbh.de>
To: linux-mtd@lists.infradead.org
Subject: Re: Cleaning JFFS2 errors
Date: Wed, 30 Jan 2008 14:23:00 +0100 [thread overview]
Message-ID: <47A07A34.6010209@mkc-gmbh.de> (raw)
In-Reply-To: <478F1509.2090001@mkc-gmbh.de>
No answer jet.
Does this mean it is a silly question or is there no solution for it?
Bernd
Bernd Büttner schrieb:
> Hi,
> after working some time with the JFFS2 filesystem (on a uclinux-system with a non-mmu freescale processor)
> I'm getting errors on every mount like this:
>
> jffs2_scan_inode(): CRC failed on node at 0x00c999f0: Read 0xffffffff, calculated 0x7621c0c4
> Empty flash at 0x00c99a3c ends at 0x00c99c00
> Empty flash at 0x0134201c ends at 0x01342200
> jffs2_scan_eraseblock(): Node at 0x01d88df8 {0x1985, 0xe001, 0x0000002f) has invalid
> CRC 0x1985e001 (calculated 0x392fe03e)
> JFFS2 notice: (13) read_dnode: node CRC failed on dnode at 0x1341fd4:
> read 0xffffffff, calculated 0xce9c70e9
>
> The kernel is 2.6.19 from the latest uclinux distribution 20070130.
>
> I think these errors are the result of power-loss, misbehaving new drivers and system crashes,
> and I suppose they are not critical and will be corrected by jffs2 after some time.
>
> But delivering such systems to customers doesn't look good.
>
> Is there a possibility to force jffs2 to correct these errors at once?
>
> I hope so.
>
> Bernd
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
next prev parent reply other threads:[~2008-01-30 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 8:42 Cleaning JFFS2 errors Bernd Büttner
2008-01-30 13:23 ` Bernd Büttner [this message]
2008-01-30 23:07 ` Jörn Engel
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=47A07A34.6010209@mkc-gmbh.de \
--to=b.buettner@mkc-gmbh.de \
--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