From: David Vrabel <dvrabel@arcom.co.uk>
To: mtd@infradead.org
Subject: JFFS corruption
Date: Mon, 07 Aug 2000 09:17:53 +0100 [thread overview]
Message-ID: <398E70B1.DB59E92D@arcom.co.uk> (raw)
Hi,
After running the following test during the weekend the JFFS filesystem
was corrupted.
copy files from dir1 to dir2
check checksums match
copy files from dir2 to dir1
check checksums match
repeat
The board would then be reset at a random time (using the hardware
watchdog).
All the files have strange stuff in them eg
EPPEAQTEPPED@ADDADUPQ@AAEPDEDAE... and so on...
Unfortunatly syslogd was logging to this partition (with hindsight I
should have logged elsewhere...) so the log was trashed but after the
corruption we have
kernel: Waiting for chip, status = 4 <-- from cfi_cmdset_0001.c
kernel: Didn't read all bytes in flash_safe_read() <-- from JFFS
several times (all at the same time). Don't know if this is relevant
since it only occured once 24 hrs after.
According to the logs of the actual test (which I did log remotely) the
corruption did not occur after a reboot but after 30 or so iterations of
the test.
David Vrabel
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
reply other threads:[~2000-08-07 8:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=398E70B1.DB59E92D@arcom.co.uk \
--to=dvrabel@arcom.co.uk \
--cc=mtd@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