[Bug 1673] New: Verbose dry run doesn't report replacements of
symlink with directory
samba-bugs at samba.org
samba-bugs at samba.org
Sat Aug 28 06:18:31 GMT 2004
https://bugzilla.samba.org/show_bug.cgi?id=1673
Summary: Verbose dry run doesn't report replacements of symlink
with directory
Product: rsync
Version: 2.6.2
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo: wayned at samba.org
ReportedBy: vanes002 at umn.edu
QAContact: rsync-qa at samba.org
After an rsync, if a directory on the target is replaced by a symlink pointing
to a new location containing the original, unchanged, directory content, a
verbose dry-run will *not* report that the directory contents from the source
will be transferred to the target and replace the symlink (which is what happens
during the non-dry-run invocation).
I discovered this during preliminary testing prior to using the new 2.6.3
--keep-dirlinks option (which, BTW, works just great in 2.6.3pre1).
This bug may be related to bug 1433.
The problem occurs with 2.6.2 (and possibly earlier) as well as with 2.6.3pre1.
Here's an example using 2.6.2:
$ ll -R a
a:
total 12
-rw-r--r-- 1 jve users 29 Feb 8 2004 f1
-rw-r--r-- 1 jve users 29 Feb 8 2004 f2
drwxr-xr-x 2 jve users 4096 Feb 8 2004 projects
a/projects:
total 8
-rw-r--r-- 1 jve users 29 Feb 8 2004 p1
-rw-r--r-- 1 jve users 29 Feb 8 2004 p2
$ rm -rf a1
$ rsync -la a/ a1/
$ rm -r a1/projects
$ ln -s ../a/projects a1/projects
$ ll -R a1
a1:
total 8
-rw-r--r-- 1 jve users 29 Feb 8 2004 f1
-rw-r--r-- 1 jve users 29 Feb 8 2004 f2
lrwxrwxrwx 1 jve users 13 Aug 28 02:10 projects -> ../a/projects
$ rsync -lavn a/ a1/
building file list ... done
wrote 146 bytes read 20 bytes 332.00 bytes/sec
total size is 116 speedup is 0.70
$ rsync -lav a/ a1/
building file list ... done
./
projects/
projects/p1
projects/p2
wrote 292 bytes read 60 bytes 704.00 bytes/sec
total size is 116 speedup is 0.33
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
More information about the rsync
mailing list