Thanks for the response. Incomplete data on server (NFS) is alright. I wanted to know what happens to the dirty cache pages (on NFS client with soft mount and sync flag not set) after the NFS client has retried for 3 times (or retrans). Will the NFS client retry or give up and clean up the dirty cache pages (and the dirty inode). Mayur On Wed, Sep 21, 2016 at 8:11 PM, Trond Myklebust <trondmy@xxxxxxxxxxxxxxx> wrote: > >> On Sep 21, 2016, at 10:19, Mayur Bajaj <mbajaj@xxxxxxxxxxxx> wrote: >> >> Hello, >> >> I have a question regarding NFS client behaviour with soft mount. I >> have gone through the code but could not figure out. Can someone >> please help me. >> >> An application is writing data via NFS client (soft mount, with sync >> mount option NOT set). The Application thinks that data written was >> successful but that is not the case. >> The NFS client will cache all the write request and flush after some >> time/threshold. The NFS sever is not responding. NFS client retries >> for 3 times (or retrans) and give up as the NFS server is not >> responding. >> >> Will this cache pages be pinned in memory for ever or freed up (marked >> clean) as the operation has failed? >> Will NFS client keep on retrying again? > > > The behaviour in the above situation is completely undefined. You may have bits and pieces of data persisted on the server or not, and cached data may end up getting resent after the EIO was returned to the application. > -- 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
