Package: rsync
Version: 3.0.9-3
Severity: normal
Tags: upstream

I've recently upgraded my backup host from squeeze to wheezy and am being bit by an issue in rsync handling the replacement of directories with symlinks.

I use rsync via rsnapshot to build backup snapshots over time using hard-links on directories. That continues to work correctly. However when I run a script using rsync directly to sync the entire backup directory with the multiple snapshot to a removable drive for offsite backup, rsync fails trying to unlink directories.

This appears to be in line with the bug documented upstream: https://bugzilla.samba.org/show_bug.cgi?id=7129

I initially thought it was a regression in the version from squeeze, however I downgraded and tested with the squeeze version with the same result, so it juts happens to be induced by the upgrade to wheezy generating the neccessary condition in my backup set.

For reference, the changes on this fairly minimal server that trigger this issue are:
        /etc/network/run
        /usr/share/doc/libncurses5
        /usr/share/doc/libncursesw5
        /usr/share/doc/module-init-tools
        /usr/share/doc/tcpd
        /usr/share/doc/udev

Then as my automatic backups are rotating the changes through the generations the list of times the error is encountered increases (one per backup day).

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: armel (armv5tel)

Kernel: Linux 3.2.0-3-kirkwood
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages rsync depends on:
ii  base-files  6.9
ii  libacl1     2.2.51-8
ii  libc6       2.13-33
ii  libgcc1     1:4.7.1-2
ii  libpopt0    1.16-7
ii  lsb-base    4.1+Debian7

rsync recommends no packages.

Versions of packages rsync suggests:
ii  openssh-client  1:6.0p1-2
iu  openssh-server  1:6.0p1-2

-- no debconf information


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to