On Tue, Sep 14, 2010 at 11:17:37AM +0200, fanpost@xxxxxxxxxxxx wrote: > Hello Group, > > I already send this post to the opensuse forum without response, > maybe you can help: > > we recognized very strange behaviour of nfs: > > Use case: > > Users access their files on different host through nfs4 (plain sys auth no kerberos sec). > They modify a c++ program and change parameters, > recompile it and execute it on different hosts for simulation. > > We now observed that sometimes even after modifying and recompiling > the binary, an o l d version of the same binary is executed > The Binary resides on a nfs share. > > 1) Write changes X to the Program and compile + execute it on PC A > 2) Write changes Y to the Program and compile + execute it on PC B > > Instead of executing Program Y on PC B results and logging shows that actually the old version > (X) is executed on PC B. > > Neither the problem nor the working execution is 100% reproducible. > Seems to have something to do with caching. If you downgrade to nfs3, or if you run echo 0 >/proc/sys/fs/leases-enable before starting the nfs server, does the problem go away? --b. -- 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
