From: hejianet <hejianet@linux.vnet.ibm.com>
To: linux-mtd@lists.infradead.org
Subject: [question]MTD:unstable bit issues?
Date: Wed, 24 Oct 2012 13:14:59 +0800 [thread overview]
Message-ID: <50877953.9040602@linux.vnet.ibm.com> (raw)
My hardware: vcs452 nandflash
my kernel:2.6.16(I know it is too old:(,but this problem seems not
relevant to the kernel version)
test steps:
1.copy a 100M file to the nand flash partition from remote client
2.use fsync to flush the mem to flash
3.use md5 to check whether the original file is different from the
copied one
4.repeat power-cuts test for 5 times, when booting up, it will check
the md5 again.
5.do step1 again
after a whole night test,(power-cut for 100 times), the step 4 failed.
1)there are some bytes changed:
-----------------------------------------------------
-original-file D0 40 E8 3E 00 00 BA 1A D0 40 0A 00 43 00 00 00
+file-in-flash D0 40 0F 41 00 00 BA 1A D0 40 0A 00 43 00 00 00
-----------------------------------------------------
2)a 4k bytes hole with all 0 in the flash file.
-----------------------------------------------------
-original-file DD AF C8 EE 57 EB 84 CE A1 7F B1 38 E7 22 51 2F
- 94 AE 77 5B 48 EA 61 8C 09 BB C5 74 6E B1 87 D2
- A9 32 8D 2A E7 7F D2 C3 DB 1A 92 E7 66 7C B8 4E
......
+file-in-flash 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
+ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
+ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
......
-----------------------------------------------------
I search google and find it might be relevant to "unstable bits
issue"(bit-flip) in nand.
I wonder is the bit-flip the possible reason to cause such a 4k all-zero
hole?
Thanks for any suggestion.
B.R.
Jia
next reply other threads:[~2012-10-24 5:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 5:14 hejianet [this message]
2012-10-24 8:13 ` [question]MTD:unstable bit issues? Thomas.Betker
2012-10-24 8:52 ` hejianet
2012-10-24 9:01 ` Thomas.Betker
2012-10-24 9:21 ` hejianet
2012-11-12 15:39 ` Artem Bityutskiy
2012-10-24 9:53 ` Jamie Lokier
2012-11-12 15:37 ` Artem Bityutskiy
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=50877953.9040602@linux.vnet.ibm.com \
--to=hejianet@linux.vnet.ibm.com \
--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