golang NFSv3 server
NFSv3 protocol implementation in pure Golang.
Current Status:
The most interesting demo is currently in example/osview.
Start the server
go run ./example/osview ..
The local folder at . will be the initial view in the mount. mutations to metadata or contents
will be stored purely in memory and not written back to the OS. When run, this
demo will print the port it is listening on.
The mount can be accessed using a command similar to
mount -o port=,mountport= -t nfs localhost:/mount (For Mac users)
or
mount -o port=,mountport=,nfsvers=3,noacl,tcp -t nfs localhost:/mount (For Linux users)
The NFS server runs on a net.Listener to export a file system to NFS clients.
Usage is structured similarly to many other golang network servers.
…Ports are typically determined through portmap. The need for running portmap
(which is the only part that needs a privileged listening port) can be avoided
through specific mount options. e.g.
mount -o port=n,mountport=n -t nfs host:/mount /localmount
This server currently uses billy to provide a file system abstraction layer. There are some edges of the NFS protocol which do not translate to this abstraction.
inode or equivalent unique identifier to reference
files in a file system. These are considered opaque identifiers here, which
means they will not work as expected in cases of hard linking.uid and gid
ownership of files. If ownership is important to your file system, you
will need to ensure that the os.FileInfo meets additional constraints.
In particular, the Sys() escape hatch is queried by this library, and
if your file system populates a syscall.Stat_t
concrete struct, the ownership specified in that object will be used.
You can also return a file.FileInfo
which doesn't vary between platforms so may be easier to deal with.Relevant RFCS: 5531 - RPC protocol, 1813 - NFSv3, 1094 - NFS
No open issues yet, or sync has not completed.