From: llandre <r&d2@dave-tech.it>
To: Matt Reimer <mattjreimer@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2: file contents in case of data CRC error
Date: Fri, 01 Feb 2008 15:01:12 +0100 [thread overview]
Message-ID: <47A32628.2070808@dave-tech.it> (raw)
In-Reply-To: <f383264b0801311142h3cbcbc91pb4e0d3a60fc78f4f@mail.gmail.com>
> up to JFFS2. I'm not sure, but I think what happened from there is
> that JFFS2 failed to decompress a block and instead of returning an
> error it left the page zeroed. You can use jffs2dump to correlate the
> offset reported in the CRC error with the problematic inode. Check the
> thread "bit flip" in October 2007.
Thanks a lot for this advice. The system is based on linux 2.4.20 and
ELDK 2.0.2 so the jffs2dump is not available out-of-the-box. I'll try to
build recent mtd-utils package.
> What platform is this on?
PowerPC 405EP.
Regards,
llandre
DAVE Electronics System House - R&D Department
web: http://www.dave.eu
email: r&d2@dave-tech.it
next prev parent reply other threads:[~2008-02-01 14:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 16:54 JFFS2: file contents in case of data CRC error llandre
2008-01-31 19:19 ` Korolev, Alexey
2008-02-01 14:00 ` llandre
2008-02-01 15:53 ` Korolev, Alexey
2008-02-01 17:43 ` Jamie Lokier
2008-02-02 17:11 ` llandre
2008-02-04 21:32 ` Jamie Lokier
2008-02-02 16:32 ` llandre
2008-02-04 14:25 ` Korolev, Alexey
2008-01-31 19:22 ` Jffss2_write_super erasing all the blocks Nikhil Bansal (nikbansa)
2008-02-02 19:30 ` SV: " Joakim Tjernlund
2008-01-31 19:42 ` JFFS2: file contents in case of data CRC error Matt Reimer
2008-01-31 22:57 ` Jamie Lokier
2008-02-01 14:01 ` llandre
2008-02-01 14:01 ` llandre [this message]
2008-02-02 17:03 ` llandre
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=47A32628.2070808@dave-tech.it \
--to=r&d2@dave-tech.it \
--cc=linux-mtd@lists.infradead.org \
--cc=mattjreimer@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.