Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

MS NFS 41 Client failed with error code 3 #2

Open
MySepultura opened this issue Jun 10, 2015 · 9 comments
Open

MS NFS 41 Client failed with error code 3 #2

MySepultura opened this issue Jun 10, 2015 · 9 comments

Comments

@MySepultura
Copy link

Dear Community,

I have a question because the NFS Client is failing with error code 3. System can't find path.

NekoDrive NFS Client Test Component is finding the the drive.

I typed:
nfsd.exe -d 3 -noldap uid 1000 gid 100

then I typed
nfs_mount z: 192.168.0.182:\home\winclient

Here the programm is failing.

Can anyone help me?
@kofemann
Copy link
Owner

Hi,
do you started command window as admin?

@MySepultura
Copy link
Author

yes. NFSD is active

@kofemann
Copy link
Owner

and it's --uid 1000 --gid 1000 and --noldap right?

@MySepultura
Copy link
Author

yes I used nfs_mount.exe -d 3 -noldap --uid 1000 --gid 100.

NekoDrive can connect with UID 1000 and GID 100 Read+Write Access.

@MySepultura
Copy link
Author

I have fixed this Problem!

@kofemann
Copy link
Owner

Great! Is there ang information missing in the readme to get it running ?

@MySepultura
Copy link
Author

yes you must set on System > Computer Name > Change > more > Primary DNS Prefix or NFSD will fail to load.

And it seems you must add "insecure" to Linux NFS Server.

@vision-ken
Copy link

@MySepultura
what's need to set to Primary DNS Prefix?

@Converter-App
Copy link

I ran into the same issue and spent hours fixing it. The solution was, that the NFS daemon (nfsd.exe) file was corrupted, therefore the service did not start properly at the system startup as it used to. Fixing all file system errors and reinstalling the daemon solved it for me.

kofemann pushed a commit that referenced this issue Jul 29, 2024
@gisburn @kofemann
daemon: Fix DrMemory "UNINITIALIZED READ" hits in |attr_cache_update()|
569d8f5 
Fix DrMemory hits in |attr_cache_update()|, which were triggered by
using the request |bitmap4| instead of the response |bitmap4|

DrMemory hits look like this:
---- snip ----
Error #1: UNINITIALIZED READ: reading 8 byte(s)
attr_cache_update                     [ms-nfs41-client\daemon\name_cache.c:323]
nfs41_attr_cache_update               [ms-nfs41-client\daemon\name_cache.c:957]
nfs41_setattr                         [ms-nfs41-client\daemon\nfs41_ops.c:1495]
handle_setexattr                      [ms-nfs41-client\daemon\ea.c:186]
upcall_handle                         [ms-nfs41-client\daemon\upcall.c:220]
nfsd_worker_thread_main               [ms-nfs41-client\daemon\nfs41_daemon.c:188]
nfsd_thread_main                      [ms-nfs41-client\daemon\nfs41_daemon.c:226]
KERNEL32.dll!BaseThreadInitThunk     +0x13     (0x00007ffe78f47374 <KERNEL32.dll+0x17374>)

Error #2: UNINITIALIZED READ: reading 4 byte(s)
attr_cache_update                     [ms-nfs41-client\daemon\name_cache.c:324]
nfs41_attr_cache_update               [ms-nfs41-client\daemon\name_cache.c:957]
nfs41_setattr                         [ms-nfs41-client\daemon\nfs41_ops.c:1495]
handle_setexattr                      [ms-nfs41-client\daemon\ea.c:186]
upcall_handle                         [ms-nfs41-client\daemon\upcall.c:220]
nfsd_worker_thread_main               [ms-nfs41-client\daemon\nfs41_daemon.c:188]
nfsd_thread_main                      [ms-nfs41-client\daemon\nfs41_daemon.c:226]
KERNEL32.dll!BaseThreadInitThunk     +0x13     (0x00007ffe78f47374 <KERNEL32.dll+0x17374>)
---- snip ----

Signed-off-by: Cedric Blancher <[email protected]>
Signed-off-by: Tigran Mkrtchyan <[email protected]>
kofemann pushed a commit that referenced this issue Sep 27, 2024
@gisburn @kofemann
build.vc19: Disable VC19 "JustMyCode" feature for better drmemory sta…
a8e797f 
…cktraces

Disable VC19 "JustMyCode" feature (see
https://learn.microsoft.com/en-us/cpp/build/reference/jmc?view=msvc-170)
for better drmemory stacktraces.

The "JustMyCode" feature has caused problems with accurate
stacktraces in libtirpc&co like this:
---- snip ----
Error #2: UNINITIALIZED READ: reading 4 byte(s)
libtirpc.dll!__CheckForDebuggerJustMyCode  [D:\a\_work\1\s\src\vctools\crt\vcstartup\src\misc\debugger_jmc.c:23]
libtirpc.dll!time_not_ok                   [msnfs41_uidmapping\ms-nfs41-client\libtirpc\src\clnt_vc.c:15732480]
KERNELBASE.dll!OpenThreadToken            +0x4c     (0x00007ffb9b992b6d <KERNELBASE.dll+0x32b6d>)
KERNELBASE.dll!SleepConditionVariableSRW  +0x36     (0x00007ffb9b9d3327 <KERNELBASE.dll+0x73327>)
nfs41_send_compound                        [ms-nfs41-client\daemon\nfs41_rpc.c:351]
compound_encode_send_decode                [ms-nfs41-client\daemon\nfs41_compound.c:153]
nfs41_read                                 [ms-nfs41-client\daemon\nfs41_ops.c:873]
read_from_mds                              [ms-nfs41-client\daemon\readwrite.c:80]
handle_read                                [ms-nfs41-client\daemon\readwrite.c:165]
upcall_handle                              [ms-nfs41-client\daemon\upcall.c:220]
nfsd_worker_thread_main                    [ms-nfs41-client\daemon\nfs41_daemon.c:188]
---- snip ----
Note the bogus line number in "clnt_vc.c:15732480", and that
|SleepConditionVariableSRW()| (system library function) cannot call
|libtirpc.dll!time_not_ok|.

We just disable this feature as it only causes confusion.

Signed-off-by: Cedric Blancher <[email protected]>
Signed-off-by: Tigran Mkrtchyan <[email protected]>
kofemann pushed a commit that referenced this issue Oct 23, 2024
@gisburn @kofemann
daemon: Fix drmemory hits when processing NFSv4 referrals
3bd2690 
Fix two drmemory hits when processing NFSv4 referrals:
---- snip ----
Error #1: UNINITIALIZED READ: reading 8 byte(s)
 0 path_fh_copy               [ms-nfs41-client\daemon\util.c:468]
 1 server_lookup              [ms-nfs41-client\daemon\lookup.c:259]
 2 server_lookup_loop         [ms-nfs41-client\daemon\lookup.c:360]
 3 nfs41_lookup               [ms-nfs41-client\daemon\lookup.c:512]
 4 lookup_entry               [ms-nfs41-client\daemon\readdir.c:468]
 5 readdir_copy_entry         [ms-nfs41-client\daemon\readdir.c:534]
 6 handle_readdir             [ms-nfs41-client\daemon\readdir.c:800]
 7 upcall_handle              [ms-nfs41-client\daemon\upcall.c:220]
 8 nfsd_worker_thread_main    [ms-nfs41-client\daemon\nfs41_daemon.c:201]
 9 nfsd_thread_main           [ms-nfs41-client\daemon\nfs41_daemon.c:239]
10 KERNEL32.dll!BaseThreadInitThunk +0x13 (0x00007ffadccb7374 <KERNEL32.dll+0x17374>)

Error #2: UNINITIALIZED READ: reading 8 byte(s)
 0 path_fh_copy               [ms-nfs41-client\daemon\util.c:470]
 1 server_lookup              [ms-nfs41-client\daemon\lookup.c:259]
 2 server_lookup_loop         [ms-nfs41-client\daemon\lookup.c:360]
 3 nfs41_lookup               [ms-nfs41-client\daemon\lookup.c:512]
 8 readdir_copy_entry         [ms-nfs41-client\daemon\readdir.c:534]
 9 handle_readdir             [ms-nfs41-client\daemon\readdir.c:800]
10 upcall_handle              [ms-nfs41-client\daemon\upcall.c:220]
11 nfsd_worker_thread_main    [ms-nfs41-client\daemon\nfs41_daemon.c:201]
12 nfsd_thread_main           [ms-nfs41-client\daemon\nfs41_daemon.c:239]
---- snip ----

Reported-by: Cedric Blancher <[email protected]>
Signed-off-by: Cedric Blancher <[email protected]>
Signed-off-by: Tigran Mkrtchyan <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kofemann @MySepultura @vision-ken @Converter-App