I have a script automatically backuping files on another Linux machine with rsync to a btrfs partition on a drive shared with Samba running on Raspberry Pi with AlARM 7. All of a sudden rsync during copying began to produce lots of errors like this:
$this->bbcode_second_pass_code('', 'rsync: failed to set times on "/mnt/backup/arch/home/al/Mail/sent/cur/1412084390.9027_3.kw:2,S": Invalid argument (22)
rsync: failed to set times on "/mnt/backup/arch/home/al/perl5/man/man3/Algorithm::Diff.3pm": Invalid argument (22) ')
All filenames in error messages contain colons. When I try to delete some of those files through a mount point on a remote machine (accessing those files via a Samba share) I get a "no such file or directory" error. When these files are accessed on Raspberry Pi where they reside, they can be deleted OK. So, one can conclude that the errors are caused by Samba's handling filenames with colons. But why those errors began to happen without evident reasons? All files in errors are rather old and haven't caused errors previously. Did some recent Samba upgrade caused this change? (Pacman reports that Samba package 4.3.0-2 was upgraded at September 22.) Did someone experience this problem?