rsync - Sep 2020 - rsync 3.1.3 dry run bug?

Since Ubuntu 20.04 (focal) the rsync option -n (Dry Run) is not working 
correctly.

---
rsync --version
rsync? version 3.1.3? protocol version 31

----

I used this command for about ten years without mayor issues:

---

rsync -vaHEiuzn --skip-compress=jpg,JPG,mov,MOV,mp4,MP4,m4v,avi,png 
--exclude=*.pyc --exclude='somedir/**/.gps.cnf' 
--exclude='somedir/**/clonezilla' --stats --delete /home/myuser/Datadir/
myuser at remotehost:/home/myuser/Datadir
sending incremental file list
.d.....g... 
somedir/Ubuntu/New_Ubuntu/scripts/focal_myuser/configfiles/myuser/
.f.....g... 
somedir/Ubuntu/New_Ubuntu/scripts/focal_myuser/configfiles/myuser/some.tar.gz

Number of files: 29,766 (reg: 23,446, dir: 6,245, link: 75)
Number of created files: 0
Number of deleted files: 0
Number of regular files transferred: 0
Total file size: 10,689,006,380 bytes
Total transferred file size: 0 bytes
Literal data: 0 bytes
Matched data: 0 bytes
File list size: 0
File list generation time: 0.001 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 1,042,788
Total bytes received: 6,703

sent 1,042,788 bytes? received 6,703 bytes? 699,660.67 bytes/sec
total size is 10,689,006,380? speedup is 10,184.94 (DRY RUN)

---


In this example output rsync says that it would just perform two group 
changes,

BUT despite the -n option it actually synced some documents.


This happened several times already but can not be reproduced easily - 
every time I noticed,

that it went wrong again and immediately made a test with a newly 
created or modified file, it worked as expected.


Best regards

Wolf

On Sun, Sep 27, 2020 at 12:27 PM Dipl.-Ing. Wolf-Dieter Pichler wrote:
> In this example output rsync says that it would just perform two
> group changes, BUT despite the -n option it actually synced some documents.
>
I doubt that very much, so I'd suggest checking on what else might be going
on.  Rsync has a bunch of safety functions with built-in dry-run checks
that keep it from making the changes that it itemizes that need to be
done.  And if it didn't even mention that a file needs to be updated,
there's no reason for it to have somehow made a secret change.  If you were
expecting to see a file change in the list of dry-run changes and it's not
there, then something prior to the rsync dry-run must have changed it.
Given that you're using -H, you might check if the affected file was linked
to a file that was recently changed in some other copy.

..wayne..
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.samba.org/pipermail/rsync/attachments/20200929/8cd9d860/attachment.htm>