1

I have a nfs server on a raspberry pi 3 b+, that share an ext4 directory. The nfs client is a windows 10 computer.

I have a problem with filename characters encoding on client side. All accent characters are displayed badly (I am a french speaker, so some words have character like 'é' or 'è' for example).

My local setting on server side was en_US.UTF-8. I have changed it to fr_FR.UTF-8 but it change nothing. It seems that nfs version used is nfs v3. But I didn't manage to force it to v4. I have tried with a share directory on a ntfs partition, it's work fine and all wharacter well displayed.

Do you know what is the root cause of this type of problem ?

2
  • Do you mean characters in the file names, or characters in the files themselves? Commented Jul 28, 2020 at 14:24
  • I mean characters in the filename
    – geo667
    Commented Jul 28, 2020 at 14:30

1 Answer 1

3

There is no nfs4 client for windows. You better try to use samba for windows clients, but keep nfs export for unix hosts in parallel.

4
  • 2
    Upvoted. Highest currently supported nfs client is nfs3 Commented Jul 29, 2020 at 0:14
  • @TimothyFrew Linux, FreeBSD have 4.2 clients. Solaris support v4.1, OSX (with some long outstanding bugs) 4.0. Windows is the only OS that supports only v2 and v3, though they have nfsv4.1 server.
    – kofemann
    Commented Jul 29, 2020 at 6:11
  • Yes I agree with you Commented Aug 6, 2020 at 0:07
  • Seriously? I have been wasting 2 weeks trying all the combinations and permutations from windows to connect to a nfs4 server and it was that windows simply can't?! And is there any user-space client for v4? Commented May 8, 2021 at 12:09

Not the answer you're looking for? Browse other questions tagged .