public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Ralph Stickley <rstickley@datalux.com>
To: "linux-embedded@waste.org" <linux-embedded@waste.org>,
	mtd-list <mtd@infradead.org>
Subject: More Compact Flash Problems
Date: Fri, 14 Apr 2000 15:58:42 -0400	[thread overview]
Message-ID: <38F77872.4399A0F8@datalux.com> (raw)


When I copy a file system to the CF, some cards work, some do not.

A problem I've noticed:
1. copy files from image fs (27MB of files) to mnt (mount point of CF)
2. sync / umount / mount
3. diff -rq mnt image reports files different

One file in particular, on one card, always comes up different:
XF86_SVGA

If I delete that file and copy the original one again, the above steps
can be
repeated...same problem.

However, if I move that file to xxxx then copy XF86_SVGA (this prevents
me 
from using the original blocks used by XF86_SVGA) -  Now it works!!

So, I conclude that either:
A. there are bad blocks on the CF device that linux is not aware of
B. the write operation is not fully supported with CF and the IDE driver


Which leads to a few questions:

1. Can you actually find bad blocks on a device ? (mkfs -c didn't seem
to help)

2. Are these cards manufactured with a list of bad blocks ?? 

3. Is there any way to slow down the copy operation ? (maybe this is not 
supporting the copying of large files - some flash blocks may take
longer to
write than others - moon phase may be a factor here :)

4. Will the nftl drivers work for CF ??

Any help on this would be greatly appreciated!
Thanks,
Ralph


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

                 reply	other threads:[~2000-04-14 19:59 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=38F77872.4399A0F8@datalux.com \
    --to=rstickley@datalux.com \
    --cc=linux-embedded@waste.org \
    --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