Will

Steps were just to plug in a 4tb luks encrypted disk, and mounting once cryptsetup was installed. Got I/O errors when trying to navigate in the file browser or list...

I wonder if https://github.com/willscott/go-nfs/pull/72 was the underlying issue behind this can you try again with the current version?

@ncw - the reason memfs does not implement lock / unlock is because the accompanying 'Network Lock Manager (NLM) protocol' is not implemented here. The protocol is documented in RFC...

* If we can get logging of the NFS calls made while opening a word document, I'm not totally convinced that the underlying issue is lack of the locking protocol...

There's a log trace on each request: https://github.com/willscott/go-nfs/blob/master/conn.go#L62

There's a major issue with NLM in this context - which is that from what i can tell mount'ing of NFS (the clients in Mac and Linux at least) don't...

* I'm working on implementing the expected verifier for exclusive mode semantics. I'll try to have that up in the next day or two * The attempt at 'Stat' that...

@ncw perhaps also try with my branch at https://github.com/willscott/go-nfs/tree/feat/exclusive-create and see if it makes a difference

I _think_ the approach i have should work in a degraded way - if there isn't an exact match, a temporary file is made to save and recover the verifier....

I think that's what that method does, right? if the `Sys()` returns a FileInfo or *FileInfo it is directly returned, rather than being parsed from the unstable OS struct.