Hello,
I came across an issue and don't know whether I made a mistake somewhere or if it's a bug.
I have a fresh installation of 11.3. I went through and setup my datasets (choosing share type SMB), permissions and SMB shares. No problem in accessing files. However, when copying data to the NAS, I noticed that file created timestamps were not syncing up (though folder created timestamps are fine). I use ROBOCOPY to preserve all timestamps to/from backups.
Interestingly, when using ROBOCOPY, all files get a created datetime of "Wednesday, 2 January 1980, 10:00:00 AM", but when copying over via windows explorer, file created datetime equals whatever the modified datetime is. In any case, even with full permissions, attempting to change a file created timestamp (with something like NewFileTime) fails.
Digging through the settings a bit more, I found under share properties that VFS Object ixnas is active by default. Removing it fixes the above problem and I can again manipulate all timestamps. In the manual, for ixnas, it states that it is an experimental object to improve ACL compatibility with Windows. So is this a bug with ixnas? What is the impact of not having it active? @anodos stated that ixnas improves directory listing performance, so I would like to have it active but I cant not be able to change file timestamps.
Edit: please see post below after additional testing.
Is this a bug or have I made a mistake in configuration somewhere?
I came across an issue and don't know whether I made a mistake somewhere or if it's a bug.
I have a fresh installation of 11.3. I went through and setup my datasets (choosing share type SMB), permissions and SMB shares. No problem in accessing files. However, when copying data to the NAS, I noticed that file created timestamps were not syncing up (though folder created timestamps are fine). I use ROBOCOPY to preserve all timestamps to/from backups.
Interestingly, when using ROBOCOPY, all files get a created datetime of "Wednesday, 2 January 1980, 10:00:00 AM", but when copying over via windows explorer, file created datetime equals whatever the modified datetime is. In any case, even with full permissions, attempting to change a file created timestamp (with something like NewFileTime) fails.
Edit: please see post below after additional testing.
Is this a bug or have I made a mistake in configuration somewhere?
Last edited: