Linux NFS development
 help / color / mirror / Atom feed
From: Peter Staubach <staubach@redhat.com>
To: Venkatesh KS <venkatesh.ks@gmail.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: novice question about large write requests
Date: Fri, 02 Feb 2007 09:12:03 -0500	[thread overview]
Message-ID: <45C346B3.4080109@redhat.com> (raw)
In-Reply-To: <4cf2912c0702020535i2b11691as8bc5ead997fa0d85@mail.gmail.com>

Venkatesh KS wrote:
> Folks,
>
> I am trying to understand how nfs client handles a server reboot while 
> issuing multiple
> unstable writes followed by a commit.
>
> Say a user requests a large write requests.
> nfs client breaks it into multiple 32k requests, each 32k write 
> request being unstable
> and finally a commit call before the nfs client returns back to the user.
>
> If the server reboots in between these write calls, will the nfs 
> client know abt it.
> The write before this may not have made it to disk. If the nfs client 
> doenst know
> abt it then it goes ahead with commit call and returns.

I would suggest checking out RFC1813 for information on this topic.

       ps

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-02-02 14:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-02 13:35 novice question about large write requests Venkatesh KS
2007-02-02 14:12 ` Peter Staubach [this message]
2007-02-02 16:10   ` Chuck Lever

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=45C346B3.4080109@redhat.com \
    --to=staubach@redhat.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=venkatesh.ks@gmail.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