Closed contentfree closed 6 years ago
I wanted to add that I could successfully copy files off of the mount to the local machine and open them just fine. (But not being able to work on the files on the mount is a showstopper w/o some serious rearchitecting…)
It's possible that https://github.com/kofemann/ms-nfs41-client/blob/edcf7feb855148751ccfecc8331d26bba268b751/daemon/open.c#L425 is part of the problem. AWS EFS (and other Linux NFS servers) disallow anything but OPEN4_SHARE_DENY_NONE
. Specifically noted in http://docs.aws.amazon.com/efs/latest/ug/nfs4-unsupported-features.html.
Does that mean I'd have to do a custom build and comment out that definition?
Yup, that fixed it. I commented out that #define
and recompiled (which was not as straight forward a task as expected… I had to use VS2010 – Couldn't get it worked out with VS2015). I also had to use certreq
instead of makecert
(because the Root Agency certificate is only 512-bit which is no longer valid).
But… I have a working NFSv4.1 client on Windows hooking up with AWS EFS. So that's cool.
Hej! Good to hear that it works for you.
I just update project to build with VS2017
https://github.com/kofemann/ms-nfs41-client/tree/vs2017
Can you give it a try?
Because AWS EFS disallows any share deny value other than OPEN4_SHARE_DENY_NONE
I had to comment out that #define
. Haven't tried with a new VS.
Hi, i try to compile with VS2017 and the project nfs41_drivers does not compile.
The error is MSB3073, the command :
call C:\Program Files (x86)\Windows Kits\10\\bin\setenv.bat C:\Program Files (x86)\Windows Kits\10\ fre x64 win7 cd /d C:\projects\ms-nfs41-client\sys build
exited with code 9009. nfs41_driver C:\Program Files (x86)\Microsoft Visual studio\2017\Enterprise\Common7\IDE\VC\VCTargets\Microsoft.MakeFile.Targets
I have the WDK 10.0.14393.0 and it seems that the SETENV.BAT does not exist anymore : https://stackoverflow.com/questions/22191837/setenv-bat-is-missing-windows
Also the command build seems to be deprecated and msbuild has replaced it...
François
I thought I was golden having installed all of this, but turns out I was wrong.
I'm not able to actually use any files. I have an NFSv4.1 mounted filesystem (AWS EFS) and I can browse the entire directory structure just fine.
I have a test file in the root – just a plain text file – but I'm unable to even open it in Wordpad:
I am able to open the same file in Notepad, but attempting to save any changes results in:
Notepad then prompts me to save it to another file. Which I'm able to do! However, once I try to edit that file, it gives me the same error message above.
Here's the debug output (default level) using
--noldap --uid 1000 --gid 1000
:There's a lot of noise in there (maybe) and TBH, I can't point attention to anything more than the big errors. I don't know why it's trying to create a file with
mod 0
though… maybe that's a clue?(I know this project is pretty much dead, but you're my only hope Obiwan)