Greetings, On a new system rsync from windows (with cygwin) to Ubuntu, I have a handful of files that repeatedly throw errors saying failed to set times invalid argument (22). I have dozens of these configurations and have never had this problem. rsync: failed to set times on "/<full path>/.ImageTest.reg.jDGIg0": Invalid argument (22) The suffix is random and changes each time. The original file is ImageTest.reg . There is no file starting with the dot or the random suffix. Time stamps are accurate and current. Permission on the source and destination directory is 777 and permissions on the source and destination file is 777. Machine times are about 1 second apart. Where is temp file coming from? Why is the set time failing? Thanks in advance, Leon -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20210124/aaf92f33/attachment.htm>
In <CAJjVFmnRrsNWH0q78ebYV2QumihxCxJyMV5R4zwv5ozdgs5udQ at mail.gmail.com>, on 01/24/21 at 07:46 PM, Leon Vanderploeg via rsync <rsync at lists.samba.org> said: Hi,>rsync: failed to set times on "/<full path>/.ImageTest.reg.jDGIg0": >Invalid argument (22)>Where is temp file coming from?They are created to hold the content of the file to be replaced during the data transfer. The names are chosen to minimize the change of naming comflicts. This is rsync's default behavior.>Why is the set time failing?Hard to say without more information. Exactly what is the failing rsync command line? What is the destination file system format? Are you running the same version of rsync on both sides of the transfer? Different platforms have different rules for timestamp granularity. This may or many not be contributing to this issue. Steven -- ---------------------------------------------------------------------- "Steven Levine" <steve53 at earthlink.net> Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------