From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Fat write problem
Date: Fri, 17 Jan 2014 15:58:50 +0100 [thread overview]
Message-ID: <m2ha92ejth.fsf@lamuella.denx.de> (raw)
In-Reply-To: <15AE5A936F5E3A42A9144E66875A0A8938AFC4@server1-derijp.CLB-Benelux.lokaal> (Ruud Commandeur's message of "Wed, 15 Jan 2014 12:15:04 +0100")
Hi Ruud,
> This week I decided to do some further research and testing regarding
> this problem.
> With the image I had from the previous time, I could immediately
> reproduce it and
> by adding more and more debug prints, I tried to find the cause. Sofar,
> I have not
> succeeded in this yet.
>
> However: later on I started testing with a freshly formatted drive (32
> MB FAT partition)
> and kept repeating the fatwrite command:
>
> fatwrite mmc 0:1 42000000 test-x 200
>
> where x runs from 1, 2,3 and further. And this way I could reproduce it
> quite easily.
> Writing always fails for the 32nd file. This is with the partition
> formatted with a 512 byte
> sector size and a cluster size of 4. If the cluster size is 1 (formatted
> by Windows),
> it already fails at the 8th file.
>
> If I create a subdirectory (from Linux) with already 24 files in it, I
> can still write 29 files
> and it fails at number 30. Also, if earlier files were deleted from the
> root-directory, they
> still count in the total number of files here.
>
> If I take out the card where u-boot fails to write new files, I can
> still add new files from
> my PC with Linux or Windows.
>
> I tested with both long and short filenames (same result), VFAT is
> enabled.
>
> I hope this gives you all some more information about this problem and
> perhaps it is even a
> known problem (limited number of files in the root directory?). I know
> it is voor FAT16, but
> that was 512 entries if I am correct.
Thanks for the extensive research into this problem. For people to
help, I think the barrier of reproducing the problem is "somewhat
high", so it occurred to me if you can help setup a very easy test for
people to work on. Would you be able to generate a small image that one
can dd to a mmc card and then immediately provoke the error? If you
don't have any hosting space, as a last resort I'd be fine for you to
put it on our wiki [1].
Cheers
Detlev
[1] http://www.denx.de/wiki/view/U-Boot/TooBigPatches
--
Golden rule #12: When the comments do not match the code, they probably are
both wrong. -- Steven Rostedt <1300126962.9910.128.camel@gandalf.stny.rr.com>
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
next prev parent reply other threads:[~2014-01-17 14:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 11:15 [U-Boot] Fat write problem Ruud Commandeur
2014-01-17 14:58 ` Detlev Zundel [this message]
2014-01-17 15:49 ` Ruud Commandeur
2014-01-21 8:49 ` Ruud Commandeur
-- strict thread matches above, loose matches on Subject: below --
2013-10-23 15:17 Ruud Commandeur
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=m2ha92ejth.fsf@lamuella.denx.de \
--to=dzu@denx.de \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.