I'm embarrassed that I don't do anything close to this for my weekly nfs-ganesha merges... I'd love to see some tools to make it easier to do more testing. I wish there was a solution that didn't require two hosts for testing NFSv3 locks against nfs-ganesha. I need to get back to the pynfs v3 tests... Another test I have run is pjdfstests, which there seem to be multiple versions of, I have repos of two versions here that are Ganesha aware. These tests include a lot of POSIX compliance so will catch permission issues and other POSIX oddities. I also haven't run them in ages... https://github.com/ffilz/ntfs-3g-pjd-fstest https://github.com/ffilz/pjdfstest The nfs-ganesha tree also has a tool to help write lock tests (and can be used for a few other things too - I recently added more flags to open so it can test most open system call invocations of interest) in: https://github.com/nfs-ganesha/nfs-ganesha/tree/next/src/tools/multilock Hmm, I should incorporate the features of Bruce's lock tests into that... The multilock tool can drive multiple clients to use system calls (so any POSIX client can be used including a local process on the server) or Gluster's libgfapi or Cephs libcephfs. Frank case this is infrastructure boot test VMs http://git.linux-nfs.org/?p=bfields/testd.git;a=blob;f=bin/do- http://git.linux-nfs.org/?p=bfields/testd.git;a=blob;f=bin/do- http://git.linux-nfs.org/?p=bfields/testd.git;a=blob;f=bin/do- result