From: Mayur Bajaj <mbajaj@maprtech.com>
To: Trond Myklebust <trondmy@primarydata.com>
Cc: List Linux NFS Mailing <linux-nfs@vger.kernel.org>
Subject: Re: NFS client behaviour with soft mount
Date: Thu, 22 Sep 2016 10:09:42 +0530 [thread overview]
Message-ID: <CAKqBuocGR2TAnpgVLGiXj9atTna9O1yUk6j2ndhbmuZ3xAnrhg@mail.gmail.com> (raw)
In-Reply-To: <509BCC61-39B7-451D-A432-373F93D11673@primarydata.com>
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@primarydata.com> wrote:
>
>> On Sep 21, 2016, at 10:19, Mayur Bajaj <mbajaj@maprtech.com> 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.
>
next prev parent reply other threads:[~2016-09-22 4:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 14:19 NFS client behaviour with soft mount Mayur Bajaj
2016-09-21 14:41 ` Trond Myklebust
2016-09-22 4:39 ` Mayur Bajaj [this message]
2016-09-22 4:55 ` Trond Myklebust
2016-09-22 4:59 ` Mayur Bajaj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKqBuocGR2TAnpgVLGiXj9atTna9O1yUk6j2ndhbmuZ3xAnrhg@mail.gmail.com \
--to=mbajaj@maprtech.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@primarydata.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).