Errors when connecting/using an NFS share from Windows 2019 server.

N

Nikole

Well-Known Member
Jun 3, 2013
41
0
46
Hello all,

I've been using PVE for some but always with local storage.I now need to connect it to an NFS server that I've built on Windows 2019 Server so I can store the VM disks.I managed to connect the PVE to the share I create in 2019 however I see those lines in the PVE syslog:

nss_getpwnam: name 'Administrators@BUILTIN' does not map into domain 'mylocaldomain'
nss_getpwnam: name '-2' does not map into domain 'mylocaldomain'

I am new to NFS and as such I don't know why those "errors" are coming up on the log.
The reference to 'mylocaldomain' I assume comes from the /etc/hosts file (or /etc/resolv.conf) as those are the only two places that this domain exists.Note that the NFS server is NOT using that domain.

Any ideas on how to fix this? Are they creating a problem?
The only "issue" that I noticed is that the speed of the filestorage is not always good.

My storage.cfg related section:

nfs: 2019_SHARE_NAS
export /HDD_PROXMOX_NFS_SHARE
path /mnt/pve/2019_SHARE_NAS
server 10.0.1.20
content snippets,backup,images,rootdir,iso,vztmpl
preallocation off
prune-backups keep-all=1

Any help is much appreciated!

Nikole
 
The reason you are not getting many/any replies is that very few people run NFS server on Windows. Even fewer if any of those people run it in conjunction with Proxmox.

PVE does not re-implement NFS. Standard Linux Kernel/userland implementation is used. So the errors you see are generic. Google search brings up a few articles that may be relevant:
https://access.redhat.com/solutions/1583473
https://serverfault.com/questions/495104/what-does-this-rpc-error-message-mean

and so forth.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
You must log in or register to reply here.
Top Bottom