F2-210 File Manager damaging file names
Posted: 08 Aug 2023, 19:07
New user here. I've had a F2-210 running for about a week now, running TOS4.2.43.
I usually access shares on the TNAS using SMB via Windows 10/11. This works fine, and I've got OneDrive sync running too.
I did notice that for some reason I had some broken office document links, where previously accessed files were showing as no longer available. Looking into this, I discovered that for some filenames that had apostrophes in the title, the filename had been changed to remove the apostrophe.
Windows doesn't mind the apostrophe, so after a bit of digging I realised that it's the File Manager on the TNAS itself that's changing the filenames without warning if the corresponding folder is browsed.
To be clear, I don't have to open the file using File Manager. Simply using File Manager to browse to a directory that has any files with apostrophes in the title results in the file being immediately renamed. This means that any Office files are potentially unavailable (or an Office file that pulls in data from another file can find the date is no longer there), music playlists are broken, code I'm writing that pulls in external files no longer works as it should.
I can't believe that simply browsing a folder can result in filenames being changed. A NAS is there to store files, not make unwarranted changes to the file structure.
I know this isn't the first time this has been raised, and I did see a thread that suggested that the issue was resolved in TOS5, but as I'm using a device with an ARM processor, the option of upgrading to TOS5 isn't currently available. However, as this is a device that is still on general sale, and therefore still supported, I think the issue needs to be resolved.
I usually access shares on the TNAS using SMB via Windows 10/11. This works fine, and I've got OneDrive sync running too.
I did notice that for some reason I had some broken office document links, where previously accessed files were showing as no longer available. Looking into this, I discovered that for some filenames that had apostrophes in the title, the filename had been changed to remove the apostrophe.
Windows doesn't mind the apostrophe, so after a bit of digging I realised that it's the File Manager on the TNAS itself that's changing the filenames without warning if the corresponding folder is browsed.
To be clear, I don't have to open the file using File Manager. Simply using File Manager to browse to a directory that has any files with apostrophes in the title results in the file being immediately renamed. This means that any Office files are potentially unavailable (or an Office file that pulls in data from another file can find the date is no longer there), music playlists are broken, code I'm writing that pulls in external files no longer works as it should.
I can't believe that simply browsing a folder can result in filenames being changed. A NAS is there to store files, not make unwarranted changes to the file structure.
I know this isn't the first time this has been raised, and I did see a thread that suggested that the issue was resolved in TOS5, but as I'm using a device with an ARM processor, the option of upgrading to TOS5 isn't currently available. However, as this is a device that is still on general sale, and therefore still supported, I think the issue needs to be resolved.