Comment 33 for bug 2007055

Awesome, thanks for the help. Could you run samba -V on the server to see the samba version running there?

And then on the client, could you run:

cat /proc/mounts

and find the line with your share to see what version of the SMB protocol it ended up using?

(It'll be a line like:
//10.0.234.59/sambashare /media/ubuntu22btrfs_sambashare cifs rw,relatime,vers=3.1.1,cache=strict
)

If you have the time and can run the same script but changing "cp -p" to "rsync -t" that would be really helpful too. This morning I started finding scenarios where one of "cp -p"/"rsync -t" would fail but not the other, depending on protocol.

(Thought I was losing my mind this morning b/c one of my reliable reproducers had stopped - turned out I had changed the SMB protocol version on the client to see if it affected my other reproducer - it didn't, so I forgot I had changed it.)