On Tue, 2007-11-20 at 13:13 -0800, Stefanovich wrote: > Hi, > > I have a problem that when uploading files to our NFS server. The > problem occurs when we overwrite a file using ftp. What happens is > that on the server the file is uploaded and updated correctly, however > on our nfs clients the file itself doesn't update, it actually retains > the information from the previous version of the file. I have tried to > remount the clients when this occurs but that doesn't fix the problem. > So far the only way I have found to correct this issue is to > physically reboot the client machines. Just wondering if anyone knows > why this might be happening, and any idea on a fix or what I am doing > wrong?
Does the new file keep the same inode number as the previous one? If so, then the problem is likely to be because you are keeping the file open while the other client is writing to it. That is forbidden in the close-to-open cache consistency model that most NFS clients implement. Cheers Trond - To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
