On Mon, Feb 23, 2015 at 3:56 PM, Chris Perl <cperl@xxxxxxxxxxxxxx> wrote: > I'm currently experiencing an issue where reading from a file that is > known to only contain ascii characters can result in the process > reading that file seeing NULL bytes (0x0) in the file that never > existed. This happens for NFSv3 clients when the file is being > updated concurrently either by another NFSv3 client or directly on the > NFS server. That's expected behaviour, yes. NFS close-to-open cache consistency semantics do not allow for concurrent access while the file is being updated. -- Trond Myklebust Linux NFS client maintainer, PrimaryData trond.myklebust@xxxxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
