meaning of "IO Error: skipping the delete...."

[Nitin Agarwal]

Thanks for replying.
As adviced by you, we again ran the command by removing the -v option. The
error it gives now is as follows:
readlink dispatcher/9/done/020119.185124.0000251489.0003: No such file or
directory

We went through our file system for finding the above file, and we found the
file name to be different. It was: "020119.185124.0000251489.3" And this file
was NOT PRESENT in the main server (source)

The same error was encountered for many files, and all the error messages were
showing the last extension of the file to be added with "000".

OUR VIEWS OVER IT:
There could be something programed in rsync which while deleting the files
(which are no longer in the main server) is adding "000" to the last
extension. (.... i mean... could be something like integer extension or
something ?????)

Kindly help me over this....

Thanks & Regards
Nitin Agarwal
NOTE: 1) PLEASE NOTE THAT WE ARE HAVING VERY LARGE FILE SYSTEM. (THE NO. OF
FILES IS VERY LARGE)
2) THE EXACT ERROR WHICH I TOLD U IN MY LAST MAIL WAS "IO Error encountered:
Skipping file deletion
Thanks
Nitin

Martin Pool wrote:

> On 23 Jan 2002, Nitin Agarwal <nitin.agarwal at timesgroup.com> wrote:
> > Hi,
> > I am Nitin from India working with a leading Indian newspaper "The Times
> >
> > of India".
> > We recently downloaded "rsync" and found it to be very useful and good
> > utility.
> > We tried to implement it between our main server and the DRS (Disaster
> > Recovery System), located in different locations, connected by leased
> > lines. The data that we want to synchronize using this utility is around
> >
> > 80 GB.
> >
>
> > We were successfull in synchronizing the data first time, but later on
> > when we tried to use the "--delete" feature (to delete the files in DRS
> > which no longer exists in the main servers) by using following command:
> > [rsync -avz --delete host::module /PPI/production]
> > we encounterd the following error:
> > [IO Error: skipping the delete.....]
> > and the rest of the process continued.
> >
> > Can you please let me know the reason & solution for the same.
>
> Yes, this means that there was an error copying one of the files.  A
> common possibility is that the process did not have permission to read
> or write one of the files.
>
> Because a problem occurred, rsync refrains from deleting any files.
>
> This is because the error may reflect a configuration problem, and we
> don't want to delete files that you may have wanted to preserve just
> because you made a mistake on the command line.
>
> If you look through the error output, or perhaps turn off -v, then you
> should see messages explaining the errors.
>
> > Thanks & Regards
> > Nitin Agarwal
>
> --
> Martin