Comment 29 for bug 2007055

> I no longer think it is the Last Access difference that is relevant,
> but rather differences in the SMB request pattern
> In Ubuntu 20 and Ubuntu 22, the packet that sets the file info has that request "wrapped'
> by create file/close file SMB messages. In Ubuntu 23.10 and arch, these wrapper create/close
> are not present in the packet that sets the file info.

Dude, that's wild stuff. In essence that means that some component is not behaving standard compliant and the fix might not just be updating the client (to send "cleaner" messages) but the server as well. Which - in my case - is running on a NetGear RN214. No idea what the underlying OS is and if anyone over there at NetGear bothers to dig into things if I point them to this thread.

Final question is how I can find out for sure if my system is still affected.
uname -r tells me:
6.5.0-14-generic
and hostnamectl:
       Icon name: computer-desktop
         Chassis: desktop
Operating System: Linux Mint 21.2
          Kernel: Linux 6.5.0-14-generic
    Architecture: x86-64
, samba -V:
Version 4.15.13-Ubuntu

Do you have any recommendation for a script that I could run to find out? Something along the lines of...

#!/bin/bash

source=~/Temp/MyFile.bin
target=/media/rn214/user/Temp/MyFile.bin

echo "Source: \"$source\""
rm -f "$source"
touch "$source"
head -c 1k </dev/urandom >"$source"
ls -la "$source"
stat "$source"

echo
echo "Sleeping 10s..."
sleep 10

echo
echo "Target (cp): \"$target\""
cp --preserve "$source" "$target"
ls -la "$target"
stat "$target"

rm -f "$target"

echo
echo "Target (rsync): \"$target\""
rsync --archive "$source" "$target"
ls -la "$target"
stat "$target"

... perhaps? Thanks for your effort, highly appreciated.