NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Character encoding, Codepages, SMB/CIFS and NFS
We've got 4 ReadyNAS in operation. The 2 oldest units run RAIDiator: v4.1.16 with Samba v.3.6.25 and cannot be upgraded anymore. Microsoft finally decided to dump SMBv1 and all machines on our netwo...
StephenBwrote:
NFSv4 is supposed to use UTF-8, however that isn't enforced in the NFS clients. And I don't think your legacy NAS supports NFSv4.
The client is the one built into Windows 10 (enabled as optionl feature). Anyone with a Windows10 machine can easily check for themselves.
The share itself is already provided by ReadyNAS, access it as follows:
\\<ipaddress-ofNAS>\c\<sharename-defined-on-NAS>
I am afraid that only ANSI and some far-eastern decoding option are available in that Windows10 NFS-client.
On the NAS "Unicode" is selected, thus everything is written to the NAS using Unicode and must be read that way by whatever device/application.
At this point I haven't found the solution yet.
I've just run in to exactly the same issue. Did you find a solution?
I don't think there is one (other than perhaps finding alternative NFS clients).
I solved the filenaming / code-page problem with the following operations on Windows 10:
- copy & verify ALL content from the NAS to some newly formated disk(s). Copyied folders and files using robocopy.
- delete ALL content on the NAS
- configure & access the NAS with the NFS-client
- copy & verify content back onto the NAS
That did it for me.
Tip: try with a few affected files first.
snahl wrote:
I solved the filenaming / code-page problem with the following operations on Windows 10:
- copy & verify ALL content from the NAS to some newly formated disk(s). Copyied folders and files using robocopy.
- delete ALL content on the NAS
If you know what files are affected, you could probably just rename them from an NFS mount, which would of course be much faster.
It'd be pretty simple to write a script to identify files on the SMB mount that can't be found on the NFS mount. Not so easy to figure out the corresponding NFS file name.
True. with the aid of a script, one would gain some time. In addition the risk-factor will raise. According to Murphy's law, all will look perfect only to find out that one or more critical file(s) was missed and that of course 3 years later.
In addition there is metadata in each file that MAY be affected as well - though I have not checked this factor.
Would be interesting to learn more about that. Check it out and post the results.
However, a time-consuming copy-process might still be the easiest and likely the safest.
After all my really old ReadyNas TL6 (made by Infrant) and ReadyNas NV+ are still serving its purpose in a Windows 10 environment as an NFS-Client. A pretty good example of real world effecitve sustainability.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
