KristijanL
Dabbler
- Joined
- Jun 28, 2013
- Messages
- 13
Hi,
Before i upgrade from 9.3 to 9.10 NFS share was working fine, but after the update i cant write to NFS share anymore and in logs i saw:
Apr 5 10:56:42 freenas notifier: Starting rpcbind.
Apr 5 10:56:42 freenas notifier: Starting nfsuserd.
Apr 5 10:56:45 freenas notifier: Starting mountd.
Apr 5 10:56:45 freenas mountd[29530]: unknown user: DOMAINuser
Apr 5 10:56:45 freenas notifier: Starting nfsd.
Apr 5 10:56:45 freenas nfsd: can't register svc name
Apr 5 10:56:45 freenas notifier: Starting statd.
Apr 5 10:56:45 freenas notifier: Starting lockd.
Apr 5 10:57:03 freenas manage.py: [common.pipesubr:61] Popen()ing:
The CIFS share is working fine, with permission working as they should, only NFS has problems.
I guess there has to be a problem with the char "\" as its missing from logs.
When i browse for the user and group under "Add Unix(NFS) Share" i can see all the users and groups of the AD.
Exports file:
/mnt/vault/media -mapall=DOMAIN\user:DOMAIN\group 10.10.13.249
is it a bug or misconfiguration on my side?
Kristijan
Before i upgrade from 9.3 to 9.10 NFS share was working fine, but after the update i cant write to NFS share anymore and in logs i saw:
Apr 5 10:56:42 freenas notifier: Starting rpcbind.
Apr 5 10:56:42 freenas notifier: Starting nfsuserd.
Apr 5 10:56:45 freenas notifier: Starting mountd.
Apr 5 10:56:45 freenas mountd[29530]: unknown user: DOMAINuser
Apr 5 10:56:45 freenas notifier: Starting nfsd.
Apr 5 10:56:45 freenas nfsd: can't register svc name
Apr 5 10:56:45 freenas notifier: Starting statd.
Apr 5 10:56:45 freenas notifier: Starting lockd.
Apr 5 10:57:03 freenas manage.py: [common.pipesubr:61] Popen()ing:
The CIFS share is working fine, with permission working as they should, only NFS has problems.
I guess there has to be a problem with the char "\" as its missing from logs.
When i browse for the user and group under "Add Unix(NFS) Share" i can see all the users and groups of the AD.
Exports file:
/mnt/vault/media -mapall=DOMAIN\user:DOMAIN\group 10.10.13.249
is it a bug or misconfiguration on my side?
Kristijan