[prev in list] [next in list] [prev in thread] [next in thread] 

List:       yaffs
Subject:    [Yaffs] Corrupted files with troll-ftpd-1.28
From:       "Karl Olsen" <karl () micro-technic ! com>
Date:       2005-03-22 13:24:15
Message-ID: 001a01c52ee2$720405c0$1f00a8c0 () KARL
[Download RAW message or body]

Hello all,

I am seeing something similar to this:
http://www.aleph1.co.uk/pipermail/yaffs/2005q1/000941.html

I am using linux-2.6.11.5 with the ARM AT91RM9200 patches and the Frank
Rowand Yaffs patches, augmented with yaffs_guts.c 1.37 --> 1.38 --> 1.39 and
yaffs_fs.c 1.36 --> 1.37 patches from cvs.  I use the troll-ftpd-1.28 server
on my board.

When I transfer a file to my board, the file is initially OK, and I can copy
it somewhere else, and the copy is also OK.  But after I unmount+mount (or
reboot), the originally transferred file is truncated to the nearest 512
byte boundary, and with large files (~700 KB), I have also seen some
512-byte zero-filled holes towards the end.  The copy of the file is still
OK.  Sync'ing or remounting read-only is not enough to show the corruption.

The workaround I am using is to not transfer files to their final
destination, but to copy them after transferring.

I am using two partitions, created with add_mtd_partitions() from my nand
chip driver, and CONFIG_MTD_PARTITIONS.  The corruption problem is on both
partitions.  The output of /proc/yaffs seems to only reflect the first
partition.

Any hints?


Kind regards,
Karl Olsen



[prev in list] [next in list] [prev in thread] [next in thread]