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.

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

Can nfs4j library be used for NFS Client implementation for 4 and 4.1 versions on prod? #97

Open
ajaysethi8789 opened this issue Dec 23, 2020 · 3 comments
Labels

Comments

@ajaysethi8789
Copy link

We want to use NFS protocol to directly connect to the NFS share for accessing the files without mounting,

so, Can nfs4j library be used for NFS Client implementation for 4 and 4.1 versions on production??

If can't, do we have some other alterative solutions for the same which supports version 4 and 4.1?

@kofemann
Copy link
Member

The current client code is in alpha state and used for server testing only. Depending on your requirements you might try to adopt it to your needs, but that might involved quite some development effort. Is it metadata operations on you need IO as well? I
have an other pet-project https://github.com/kofemann/nfs41-nio2 that aims to provide java NIO2 filesystem provider that talks NFSv4.1, but it's in very early stage.

An alternative might be https://github.com/sahlberg/libnfs.

@TekCoder31
Copy link

TekCoder31 commented Jan 10, 2023

Can we use this now for client implementation fully now?

@kofemann
Copy link
Member

The client code is still in alpha state as the library is developed with the main focus on server functionality. However, it contains all building blocks for upload and download files. For example, dCache's NFS proxy is implemented based on it

https://github.com/dCache/dcache/blob/master/modules/dcache-nfs/src/main/java/org/dcache/chimera/nfsv41/door/proxy/NfsProxyIo.java

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants