Bug 1605 - Copy from NTFS to VFAT produces mkstemp and stat errors
Copy from NTFS to VFAT produces mkstemp and stat errors
Product: rsync
Classification: Unclassified
Component: core
x86 Linux
: P3 major
: ---
Assigned To: Wayne Davison
Rsync QA Contact
Depends on:
  Show dependency treegraph
Reported: 2004-08-11 21:47 UTC by Dan Barrett
Modified: 2005-03-16 16:48 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Dan Barrett 2004-08-11 21:47:20 UTC
When I run rsync on a Linux machine (SuSE 9.1 with kernel
2.6.5-7.9.5-smp), copying from an NTFS partition to a VFAT partition,
I get tons of errors from "mkstemp" like these:

mkstemp "/mnt/backup/lisa/g/Work/Mac_Home/CONFERENCE PAPERS/ISSPR/HLM ATT RUNS/\
.att19 out.m31kTI" failed: No such file or directory
mkstemp "/mnt/backup/lisa/g/Work/Mac_Home/CONFERENCE PAPERS/ISSPR/HLM ATT RUNS/\
.att2 out.54lonG" failed: No such file or directory

The NTFS partition is on a real Windows XP machine elsewhere on the network,
mounted on the Linux box via samba. The copy command is:

rsync -rtv /mnt/xp/machine /mnt/backup/lisa

where /mnt/xp/machine is the samba-mounted XP NTFS disk and
/mnt/backup/lisa is the local VFAT partition.

Is this a limitation of the filesystems or an rsync bug?
Comment 1 Dan Barrett 2004-08-11 21:55:37 UTC
I also get plenty of "stat" errors like this:

stat "/mnt/backup/lisa/g/Work/PC/DataAnal/AttS94/Old analyses/CONFLICT.HLM"
failed: No such file or directory
Comment 2 Dan Barrett 2004-08-11 22:05:14 UTC
The problem might be related to capitalization of the file path. The files named
in the error messages are indeed being copied (at least some of them -- haven't
checked all) but with different upper/lower casing. Perhaps rsync is creating
the file with one casing, then checking for its existence with different casing,
and therefore the mismatch prevents it from finding the file?
Comment 4 Dan Barrett 2004-08-11 22:21:46 UTC
Yep, adding iocharset=iso8859-1 as a mount option for the VFAT filesystem cures
the problem. It's a 2.6.5 kernel bug.
Comment 5 Wayne Davison 2004-08-12 00:10:08 UTC
Thanks for figuring out this is really a kernel bug.