I remember seeing this happen when I first set up my rsync distribution. It
turned out to be a permissions problem on the remote, though not reported as
such - as Dave suggested below. It just wouldn't delete the file. Fixed the
permissions, and then deletion went fine.

I started with a small set of files and directories with few options and worked
my way up until I got what I really wanted.

Jeff

Dave Dykstra wrote:

> On Tue, Dec 19, 2000 at 10:02:08AM +0100, Ferran Jorba wrote:
> ...
> > What *did* make a difference is to rsync a single directory, and, thus,
> > not using any --exclude directory.  Obsolete files (and directories) were
> > effectively removed:
> >
> > rsync \
> >         --verbose \
> >         --verbose \
> >         --verbose \
> >         --stats \
> >         --archive \
> >         --relative \
> >         --cvs-exclude \
> >         --delete \
> >         --delete-exclude \
> >         --compress \
> >         --rsh=ssh \
> >         [EMAIL PROTECTED]:/usr /home/fjorba/kiosk/obscured.uab.es/
> >
> > So, as a workaround, I may have to rsync each of the interesting
> > directories.  However, my opinion is that this could be considered
> > a bug, that would be nice to be fixed.
> >
> > Do you agree?
>
> No, that doesn't make sense to me.  Maybe it is somehow running into a
> problem in one of the directories that it isn't reporting, I don't know.
> My suspicion is that if you do all the directories one by one you'll find
> one of them doesn't delete.
>
> I also suspect that it's going to be very difficult for somebody other than
> you to get to the root cause of the problem because nobody else will be
> able to reproduce it.  I tried making a small example with multiple
> directories and your options and it worked fine.  If you can come up with a
> small example that reproduces the problem then it should be easy for somebody
> to come up with a fix.
>
> - Dave Dykstra


Reply via email to