From: Kjetil Aamodt <kjetil.aamodt@tandberg.com>
To: undisclosed-recipients:;
Subject: MTD/YAFFS2 page problem, data missing
Date: Wed, 19 Dec 2007 15:30:44 +0100 [thread overview]
Message-ID: <47692B14.5040205@tandberg.com> (raw)
>From time to time we have seen data corruption on our nand flash. Closer investigation with a 300MB large file showed us that 32 of 98 write-boot-read cycles got corrupted. The corruption were of two very similar forms:
a) Somewhere in the image one complete page, page M, were replaced by the contents of M+1. Page M+1, and all other data in the file were correct (data from the same page is returned twice).
b) Somewhere in the image there were two consecutive page errors. In the corrupted file page N were missing and replaced with N+1. Page N+1 contained only zeros. The rest of the data in the file were correct.
Our Linux kernel version are 2.6.22.1. The YAFFS version is per CVS of November 13. 2007.
Have anyone else seen such behavior with MTD and/or YAFFS2?
Do you have any suggestion in how to debug this?
Best regards,
Kjetil Aamodt
TANDBERG
next reply other threads:[~2007-12-19 14:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 14:30 Kjetil Aamodt [this message]
2007-12-19 18:17 ` MTD/YAFFS2 page problem, data missing falls huang
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=47692B14.5040205@tandberg.com \
--to=kjetil.aamodt@tandberg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox