search

dCache / nfs4j

Pure Java NFSv3 and NFSv4.2 implementation
Other
239 stars 75 forks source link

Can it work on windows? #46

Open Abbreviation-g opened 7 years ago

Abbreviation-g commented 7 years ago

Actually I need to start the server on the windows and start the client connection to the server on the liunx. But I don't know how?

kofemann commented 7 years ago

Can you elaborate bit more what doesn't work?

Abbreviation-g commented 7 years ago

I mean, how to implement the VirtualFileSystem. It's any demo of VirtualFileSystem implementation?

kofemann commented 7 years ago

A week ago commit 06999e77 have added javadocs for VirtualFileSystem

aasenov commented 6 years ago

The only thing that I've noticed as difference when working under Windows is when I use "NFS client for WIndows" that enable connecting to NFS server trough Windows Explorer. The thing is that this client under Windows Server 2012 R2 is compatible with NFSv3. I've researched a problem listing my file system mounted using NFSv3 server (I've mounted it under Linux, as Windows client is impossible to debug). It faced out that the NFS client is complaining if Inode of the files/folders contain more than 64 bytes. I've checked the client implementation itself and it checks against NFS3_FHSIZE value, which according to this file: https://github.com/spotify/linux/blob/master/include/linux/nfs3.h is 64 bytes. I was using Inode of size 96 bytes and when I lower it to 64 everything works like a charm. So if you plan to support both NFSv3/NFSv4 your Inode size should be at most 64 bytes.

aasenov commented 5 years ago

I've tried running the server under Windows, but there was problem mounting using NFSv3, cause mount path was resolved with Windows drive letters. I've applied the following patch and it seems to work. windowsMountServer.txt