Hello, Does NFSv4 close-to-open consistency on the client work with server "async" mount open? We see several build errors here with parallel GNU Makefile update, where one process writes a file, exists, and the next process doesn't see all data (linker ar: file too short). But if you manually look at it the files are OK, and completely written. What is this? NFSv4 client bug, NFSv4 server bug, admin error (async breaking close-to-open consistency? Also, is close-to-open consistency guaranteed between different NFSv4 clients? Thanks, Martin
