From: mhowe@cwlinux.com (Morgan Howe)
To: linux-arm-kernel@lists.infradead.org
Subject: USB Mass Storage write problem
Date: Fri, 1 Oct 2010 16:00:35 +0800 [thread overview]
Message-ID: <20101001160035.7c67e481@morgan> (raw)
Greetings,
We're working on an mx27 based board with 2 SD cards mounted as USB
mass storage devices. The test we are doing is basically as follows:
1) Copy 1MB file to SD1
2) Copy same file from SD1 to SD2
3) sync
.. Repeat until disk full
During the test process nothing will ever report failure, however,
after the test completes, doing an MD5 check of the files will show
that some files were not written properly. The file sizes are all
correct, but checking the contents we can see that in the bad files, at
some arbitrary point in the file it will stop writing the actual data
and the rest of the file will just be zero-filled. The subsequent files
after the bad one will be perfectly fine for a while (usually >1GB
worth of files) and then randomly another file will get corrupted in
this manner. Using 2 16GB SD cards we usually see around 2-6 bad files
for a full test run (until disk full). We have tested this in both the
2.6.22.6 kernel and 2.6.35.
Has anyone experienced anything like this or have some idea where to
look? I found this thread[1] which seemed related, but I'm running the
test program for that issue and so far no errors reported. Any
suggestions would be appreciated.
Regards,
Morgan
[1] http://lkml.org/lkml/2010/3/4/220
next reply other threads:[~2010-10-01 8:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 8:00 Morgan Howe [this message]
2010-10-01 8:49 ` USB Mass Storage write problem Baurzhan Ismagulov
2010-10-07 8:09 ` Morgan Howe
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=20101001160035.7c67e481@morgan \
--to=mhowe@cwlinux.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).