Bug 129631

Description of problem:
1) I mounted my FAT32 volume on my Win2K dual-boot machine:
"mount /dev/hda dos -o uid=user,gid=user"
2) I mounted a SAMBA filesystem
"mount //server/share samba -o ro,user=roshare"
3) Run my program. My program traverses the directory tree in both 
the SAMBA volume and the FAT32 volume and makes sure the two contain 
exactly the same files and directories. If there are files or folders 
in the source that do not appear in the destination (or binary 
comparison fails) then the files (and/or folders) are copied from the 
source to the destination. When the program run is complete, the 
FAT32 directory tree should be an exact copy of the SAMBA tree.

My program runs into problems when using folder names with extended 
characters (like accented characters). I use readdir() to get 
filenames (which I store in a char array) and then do a mkdir() to 
create the folders. I use fread() and fwrite() to copy the files.

I observed the problem in the following way:

A comparison between the same folder name on the SAMBA and the FAT32 
volumes failed (even though the names were the same to Win2K), 
prompting my program to create a new folder with the name retrieved 
from the SAMBA share.

When the directory was created, all the extended characters were 
replaced with "?". After some time, the FAT32 volume started behaving 
strangely, giving I/O errors on writing files and read only device 
errors, when it was clearly mounted rw. Unmounting the FAT32 volume 
and remounting it makes the problem go away. I don't know how many 
folders/files it takes before the problem reappears as this is a 
batch program copying tens of thousands of files and thousands of 
folders.

I have been running this program under Cygwin for many months without 
problem, so I rebooted into Win2K to run the program again and that 
is when I noticed the filesystem corruption. When Win2K repaired the 
disk, it complained about invalid allocation units for each of the 
folders in question and all the files in each folder were lost.

As this is a slave machine that is synchronizing to a file server, I 
tried repeating the problem and was able to get filesystem corruption 
each time (but I couldn't tell if the same folders or different 
folders were lost each time).


Version-Release number of selected component (if applicable):
kernel-2.6.7-1.494.2.2

How reproducible:
Every time.

Steps to Reproduce:
(See description)
  
Actual results:
File system corruption. Directory strings compare as not equal on 
FAT32 and SAMBA shares when they should be identical.

Expected results:
No filesystem corruption, at least.

Additional info:
Marking bug as high priority as I get file system corruption.