NFS Issues - chown command return invalid argument

[yucong111]

truenas provides two directory for nfs client (different client)

/mnt/dev1/docker
/mnt/dev1/jenkins

truenas nfs /etc/exports

root@freenas[/mnt/dev1/jenkins]# cat /etc/exports
V4: / -sec=sys
/mnt/dev1/docker -maproot="root" 192.168.10.120 192.168.10.121 192.168.10.122 192.168.10.123 192.168.10.124 192.168.10.125 192.168.10.126 192.168.10.127
/mnt/dev1/jenkins -maproot="root" 192.168.3.106

The problem is 192.168.10.120~127 mount the directory and execute command chown is ok, but 192.168.3.106 execute command return error.

192.168.10.120:

[root@node1 docker]# chown root.root 1111
[root@node1 docker]#

192.168.3.106:

[root@localhost jenkins_home]# chown root.root 111
chown: changing ownership of ‘111’: Invalid argument

Two nfs client system is centos7 , and mount info:

192.168.10.16:/mnt/dev1/jenkins nfs4 11668940544 261888384 11407052160 3% /var/jenkins_home

192.168.10.16:/mnt/dev1/docker nfs4 11755954560 348896128 11407058432 3% /docker

Nfs server is already set 'NFSv3 ownership model for NFSv4'. All the settings are the same, and all the nfs client mount is also based on the nfsv4 protocol. Why do some clients return error?

 

[anodos]

What client and server versions? Try turning up logging on NFS server and client and maybe see what op is actually failing. Maybe also use strace or truss to see what syscall is failing with EINVAL.

 

[yucong111]

What client and server versions? Try turning up logging on NFS server and client and maybe see what op is actually failing. Maybe also use strace or truss to see what syscall is failing with EINVAL.

Hi，This may be a mount error, I restarted the client machine and mount again, this time there is no error