Are you on the latest version of rsync? If so, it would help if you could
create a simple example that you could explain so we could reproduce it.
- Dave Dykstra
On Wed, May 29, 2002 at 01:43:11PM -0700, Bill Houle wrote:
> FWIW, I ran without -x and still get the same error
>
> --bill
>
FWIW, I ran without -x and still get the same error
--bill
> Does it happen if you don't use '-x'? If both directories are on the
> same filesystem, you shouldn't have any need for it.
>
> I'm not sure what the specific problem is, but I do see that the
> skip_filesystem() function call
Does it happen if you don't use '-x'? If both directories are on the
same filesystem, you shouldn't have any need for it.
I'm not sure what the specific problem is, but I do see that the
skip_filesystem() function calls link_stat so perhaps somehow the
empty string is getting passed in there.
-
OK, but I'm not exactly sure what I'm looking for...
I don't think the link error is caused by my data (I have no symlinks).
For whatever reason, it appears that a blank is leading the file list,
and the 'stat' on NULL is what is causing the link_stat error.
write(1, " b u i l d i n g f i l".
I suggest running truss -f -o trussfile before that command and look for
the error in the trussfile and see what's happening just before it. Under
some circumstances rsync can print that message when a symlink goes
nowhere, but I'm not sure what the circumstances are. Perhaps it does that
becaus
/usr/local/bin/rsync \
-axv --delete \
"${MAINDIR}/${FSERVER}/" \
"${MAINDIR}/${TSERVER}/"
Both locations are on the same (non-NFS) partition.
All old files are updated and new files copied, but the orphans
are never deleted...
--bill
> What is the command you are run
What is the command you are running?
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On
> Behalf Of Bill Houle
> Sent: Monday, 1 January 1601 11:00 AM
> To: [EMAIL PROTECTED]
> Subject: I/O error when deleting files
>
>
> When I run rsync in "no-op" mode, al
