From: "Brian T" <btuch@usa.net>
To: <linux-mtd@lists.infradead.org>
Subject: CRC failed on node ....
Date: Tue, 20 Sep 2005 17:21:32 -0500 [thread overview]
Message-ID: <012801c5be31$a90e5190$fd0ba8c0@briantpc> (raw)
Running the 2.4.20 kernel, after a power outage 2 of my test units get boot
message mount errors:
jffs2_scan_dirent_node(): Name CRC failed on node at 0x00b620c8: Read
0x640c8ca3, calculated 0x795111fe
jffs2_scan_dirent_node(): Name CRC failed on node at 0x00eaf1e0: Read
0x16f2116a, calculated 0x0622ba51
The units seem to boot fine, but I'm sure there are probably files I can no
longer access on the file system.
Is this possibly from JFFS2 running garbage collection when the power is
removed? Is there an MTD utility to fix this corruption _while_ the ROM is
mounted? Is there a work around ( like running "sync" every 5 minutes in
cron )?
Thanks,
-Brian
next reply other threads:[~2005-09-20 22:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 22:21 Brian T [this message]
2005-09-21 13:01 ` CRC failed on node Artem B. Bityutskiy
2005-09-21 15:29 ` Brian T
[not found] <A61771BC4AE2DD41B460E8D73082E6E307AA30FF@olympus.hekimian.com>
2005-09-21 1:43 ` Brian T
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='012801c5be31$a90e5190$fd0ba8c0@briantpc' \
--to=btuch@usa.net \
--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