J. Bruce Fields wrote: >> Wether or not it has anything to do. The file has been written to the >> NFS-server from another NFS-client. The server is running 2.6.31.5 and >> the client that above was run on is 2.6.24-24 (Ubuntu Jaunty), the >> client that wrote the file was running 2.6.29.1. > > I this v3 or v4? What's the exported filesystem? (ext3?) v3 and ext3 > It's probably a timestamp resolution problem; if the directory was > modified twice in the same second, the later change won't change the > timestamp, and so the client may assume its cache is still good. That's not nice.. but given the situation is may quite well be the problem. > Recent clients try a little harder to work around this. How recent and how much harder? > On the server > side it should help to switch to a filesystem with better than 1-second > timestamp resolution. Converting filesystems takes time, the one with people $HOME on was expected to be the last one to get "upgraded". Jesper -- Jesper -- 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
