On Fri, 29 Aug 2008, Theodore Tso wrote:
Can someone create a small filesystem: dd if=/dev/null of=/tmp/sample.img bs=1k count=32768 /sbin/mkfs.ext3 -F /tmp/sample.img mkdir /sample mount -o loop /tmp/sample.img /sample ... and then create some of these files for me, and then unmount the filesystem, bzip2 it, and send it to me?
The problem seems not to be reproducable simply by creating similarly named files or even copying the whole directories. The problem shows with the full 25GB data set of mine (for me), but not if I just check which directories were problematic on ARM and copy just those to eg. USB stick.
As explained in the long quotations in Martin's e-mail, when the problem is visible (I've ca. the same 25GB of data on two different disks, and the problem is shown on both disks in that directory), ls -U shows the problematic directory entires in a sequential order, but they are different on a different disk - meaning it's not the names or data as such, but where/how they are positioned on the disk + ext3 data somehow.
Of course feel free to try to reproduce something that fits on a USB stick or so, I'll try to do that again too.
-Timo