nharrington
Dabbler
- Joined
- Feb 26, 2020
- Messages
- 10
This past weekend I migrated from a Netgear ReadyNAS system to FreeNAS. The migration went pretty smoothly, but since migrating, I have discovered an issue with the "modified" timestamp on files copied from Windows getting changed to the date/time of the copy, rather than being preserved as the date/time that the file was last changed.
Note that all of the timestamps associated with the migration to FreeNAS are correct; I'm referring to the timestamps of files that I copy from Windows to FreeNAS now that the migration is complete.
I have tried copying files using the COPY command, the XCOPY command, Windows Explorer, and the ROBOCOPY command.
When files are copied from a local Windows drive to a local Windows drive, the modified timestamps are preserved regardless of which method I used to copy the files
When files are copied from a local Windows drive to an SMB share on FreeNAS, files copied with COPY, XCOPY, and Windows Explorer all have their modified timestamp updated to the date/time that the copy occurred; only ROBOCOPY appears to preserve the modified timestamp of the file.
I have confirmed this behavior on Windows 10 Professional v18363 and Windows 7 Professional w/SP1.
The fact that ROBOCOPY is able to preserve the modified timestamp indicates that doing so is possible with the share as it is configured, but why is ROBOCOPY the only method of the four that actually preserves the timestamp?
Is there a setting in FreeNAS, the SMB service, the SMB share, or somewhere else that is causing COPY, XCOPY, and Windows Explorer to not preserve the timestamp? How can I fix this?
FreeNAS-11.3-U1, 72GB RAM, 8x2TB SATA RAID-Z2
VFS Objects on SMB share = fruit, ixnas, streams_xattr
Copies from local drive to local drive using (left to right) COPY, Windows Explorer, ROBOCOPY, and XCOPY
(All Modified timestamps are preserved):
Copies from local drive to FreeNAS SMB share using (left to right) COPY, Windows Explorer, ROBOCOPY, and XCOPY
(Modified timestamp only preserved by ROBOCOPY):
Note that all of the timestamps associated with the migration to FreeNAS are correct; I'm referring to the timestamps of files that I copy from Windows to FreeNAS now that the migration is complete.
I have tried copying files using the COPY command, the XCOPY command, Windows Explorer, and the ROBOCOPY command.
When files are copied from a local Windows drive to a local Windows drive, the modified timestamps are preserved regardless of which method I used to copy the files
When files are copied from a local Windows drive to an SMB share on FreeNAS, files copied with COPY, XCOPY, and Windows Explorer all have their modified timestamp updated to the date/time that the copy occurred; only ROBOCOPY appears to preserve the modified timestamp of the file.
I have confirmed this behavior on Windows 10 Professional v18363 and Windows 7 Professional w/SP1.
The fact that ROBOCOPY is able to preserve the modified timestamp indicates that doing so is possible with the share as it is configured, but why is ROBOCOPY the only method of the four that actually preserves the timestamp?
Is there a setting in FreeNAS, the SMB service, the SMB share, or somewhere else that is causing COPY, XCOPY, and Windows Explorer to not preserve the timestamp? How can I fix this?
FreeNAS-11.3-U1, 72GB RAM, 8x2TB SATA RAID-Z2
VFS Objects on SMB share = fruit, ixnas, streams_xattr
Copies from local drive to local drive using (left to right) COPY, Windows Explorer, ROBOCOPY, and XCOPY
(All Modified timestamps are preserved):
Copies from local drive to FreeNAS SMB share using (left to right) COPY, Windows Explorer, ROBOCOPY, and XCOPY
(Modified timestamp only preserved by ROBOCOPY):