Hi,
Would it be acceptable to patch make_file() in flist.c to ignore any
ENODEV's and not mark them as io_error=1?
In afs, a mountpoint to a volume which does not exist gives an
ENODEV. As such, it can't be copied, so should (or could) just be
ignored?
The io_error isn't terminal, but it does
>>>>> "k" == Kevin J Walters <[EMAIL PROTECTED]> writes:
k> I've just created a small directory as an example, it holds a file and
k> two symlinks that don't point to anything, and another symlink going
k> nowhere in a subdirectory.
k> rsync
Hi,
I've just created a small directory as an example, it holds a file and
two symlinks that don't point to anything, and another symlink going
nowhere in a subdirectory.
rsync (2.5.5) is happy to copy these but produces an error. I can't
see why it considers this an error? It's not even abort
