Files truncate on vfat filesystem

Quoted 5 lines · Sumit Narayan

I think the problem that you are facing is because you umount the disk immediately after transferring the file. Though ls indicates that the file has been transferred, and the size match, the transfer would still be in progress behind the scene, and once you umount, and remove the USB disk, the data is lost, since the transfer was not complete.

That is definitly not the problem... i have mounted both with and without the sync option, and umount usually hangs until all buffers are flushed to the disk.

Quoted 2 lines

You are facing this problem randomly, depending on how long you wait after the transfer to remove the disk.

yes, i usually have the disk mounted all the time it is connected to my computer, and umount/mount is just somthing i use to check if the files got transferred correctly

Quoted 2 lines

This happens when you are transferring large files, and not while using small files.

size doesn't matter at all with this problem... files ranging from under 1k in size to well up under 1GiB have been truncated

Quoted 2 lines

This will happen even when you are transferring large files from your CDs.

never tried to copy from my cd.

Quoted 2 lines

I hope this helps. Just wait for few seconds after the transfer is done, and you wont lose your data anymore.

sorry to report that your input didn't help at all.

Quoted 52 lines

Regards,
Sumit
--

Quoted 44 lines · On 06 May 2003 17:29:12 +020 Peder Stray wrote:

I have a 250GB usb-storage disk i use to transport large files between work and home, I uses vfat (since I haven't found any other good filesystems that don't require me to either be root or have all files worldreadable). Anyways...

Some files get its size truncated to 0 after a while (usually a few minuts, or when i umount the disk). They seem to be the correct size when I do ls -l immediately after i have transfered the files (with cp or rsync, doesn't really matter). Moving files on the disk with mv also seems to trigger the problem sometimes.

I see that blocks get allocated, but the filesizes are 0. Currently there is a difference of 17GB in the output of df and du.

I have also noticed that the size of some directories get truncated too, thus all files copied or moved into those directories dissappear. ls -l in those directories doesn't even show . and ..

it seem very inconsistent which files are affected, both in size, length of filename, unusual characters or depth in the filestructure. No messages from the kernel logs.

A check of the filesystem from XP reports no errors in the filestructure, and it work 100% there.

kernel versions used are are amongst 2.4.18 and 2.4.20, selfcompiled or stock from RH.

More details can of course be supplied if anyone have any ideas what to check and how.

any comments or help would be much appreciated as the loss of data i experience is more than a little annyoing.

--
Peder Stray

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Quoted 4 lines

____________________________________________________________
Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005

Signature · 1 line

 Peder Stray