Files Copied to SMB Shares Have File Modified Time Adjusted
Description
I have a TrueNAS-12.0-U6.1 SMB share that I mount on a Linux machine that runs SyncThing. I then use this share from a Windows machine with SyncThing running.
The SyncThing share complains because the modified time changes on every file that gets copied into the share.
I marked this as HIGH, because it affects any new files created and effectively makes using the share as a backup device that relies on modified times to be ineffective.
Responded on the forums directly. Sorry, the holidays have been crazy.
Andrew Walker
December 30, 2021 at 11:33 AM
Sorry. I didn't have time to circle back around to this. The PCAP is a little unexpected. The last time I saw an error like this it was related to basically SMB2 request to explicitly set time (the op I was testing and verified worked). This case appears to be failure to open the file (failed with STATUS_OBJECT_NAME_NOT_FOUND) and then client client creating file and writing to it. Perhaps client removed file before you performed PCAP? Otherwise, it's possible that the particular combination of permissions and flags on operation is causing it to fail unexpectedly.
Can we schedule a teamviewer session so that I can investigate this?
I have a TrueNAS-12.0-U6.1 SMB share that I mount on a Linux machine that runs SyncThing. I then use this share from a Windows machine with SyncThing running.
The SyncThing share complains because the modified time changes on every file that gets copied into the share.
Looks like this issue, https://jira.ixsystems.com/browse/NAS-107005 has resurfaced.
I marked this as HIGH, because it affects any new files created and effectively makes using the share as a backup device that relies on modified times to be ineffective.
There's also a post on the forums here: https://www.truenas.com/community/threads/modified-timestamp-issue-on-12-u6-1-on-smb-share.96895/
Forgive me if this is a dupe, but I couldn't find one related to 12.0-U6.1.