Dear NFS gurus, we run into situation, where client gets BAD_COOKIE on a readdir. Before I go and try to adopt our server to handle it, let me describe the situation. A client node (we have seen it with RHEL6 and Ubuntu 12.04, but probably others affected as well) send a bunch of readdirs to the server. After some time (this many be hours, days ) client sends an other set of readdirs. But it reuses cookie verifier from the first readdir sequence. Server sends back BAD_COOKIE, but client never starts over with a cookie and verifier being zero. As a result, inconsistent listing and anhappy user: [exflserv04] ~ $ ls /pnfs/desy.de/exfel/disk/LCLS/2015/RAW/XCS/xcsh8215/xtc/ ls: reading directory /pnfs/desy.de/exfel/disk/LCLS/2015/RAW/XCS/xcsh8215/xtc/: Unknown error 523 Is this behavior of the client correct? Thanks a lot, Tigran. -- 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
