From: Chuck Lever <chuck.lever@oracle.com>
To: Peter Staubach <staubach@redhat.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: novice question about large write requests
Date: Fri, 02 Feb 2007 11:10:59 -0500 [thread overview]
Message-ID: <45C36293.2080201@oracle.com> (raw)
In-Reply-To: <45C346B3.4080109@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 951 bytes --]
Peter Staubach wrote:
> 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.
There is also some explanation of this in the Linux NFS FAQ:
http://nfs.sourceforge.net/
and we've found Brent Callaghan's "NFS Illustrated" to have some useful
explanation of reboot recovery with unstable writes.
[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 265 bytes --]
begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture Linux Projects Group
email;internet:chuck dot lever at nospam oracle dot com
title:Principle Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
version:2.1
end:vcard
[-- Attachment #3: Type: text/plain, Size: 374 bytes --]
-------------------------------------------------------------------------
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
[-- Attachment #4: Type: text/plain, Size: 140 bytes --]
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2007-02-02 16:14 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
2007-02-02 16:10 ` Chuck Lever [this message]
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=45C36293.2080201@oracle.com \
--to=chuck.lever@oracle.com \
--cc=nfs@lists.sourceforge.net \
--cc=staubach@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.