I
wouldn't say that FAT32 is "lenient", HOWEVER
it is
almost certain that NTFS is extremely dependent on there not being ANY errors
anywhere else, or VERY bad things will be done.
Cheap
shot, if you can identify files (or clusters of files) is to rename the stuff
something like BAD-DATA
Hi,We are using Rsync version 2.6.8 protocol version 29 on a winNT box to backup a linux (RedHat 9.0) box (same version of rsync) and everynight a different file on the NT server is reported as being corrupt, there are no errors in the rsync logs on either side. NT Event log records:
Event Type:
Wild
guess, but that sounds a lot like a disk drive going bad.
An
error message like The file or
directory is corrupted and unreadable.
There
is essentially no way that an application (including rsync)
can
cause that kind of thing.
You
probably can cause that by messing with the
Hi Tony,the volume was previously a FAT32 before it was reformatted to NTFS. I've wonderedabout the drive being dodgy, is it that FAT32 is more leanient in terms of file errors?thanks.Darrin.
On 5/12/06, Tony Abernethy [EMAIL PROTECTED] wrote:
Wild
guess, but that sounds a lot like a disk
