On Thu, Nov 16, 2023 at 1:30 PM Benjamin Coddington <bcodding@xxxxxxxxxx> wrote: > > On 16 Nov 2023, at 2:11, Martin Wege wrote: > > > Hello, > > > > Does NFSv4 close-to-open consistency on the client work with server > > "async" mount open? > > Yes, I believe it should, but I am looking at knfsd code and I think it > won't. What does that mean? nfsd server bug? > > > 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? > > Hard to say, a wire capture would show. My guess is that the server's > "async" disables the write gather in nfsd_vfs_write(). What is the correct option in Linux /etc/exports to enforce NFSv4 standard conformance? > > Also, is close-to-open consistency guaranteed between different NFSv4 clients? > > Yes. How does it work in a NFSv4 client implementation? Thanks, Martin
