From: Wendy Cheng <wcheng@redhat.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
chuck.lever@oracle.com, nfs@lists.sourceforge.net,
NeilBrown <neilb-YbfuJp6tym7X/JP9YwkgDA@public.gmane.org>
Subject: Re: [NFS] NFS Digest, Vol 18, Issue 70 (NFS performance problems)
Date: Fri, 30 Nov 2007 11:27:16 -0500 [thread overview]
Message-ID: <475039E4.5070903@redhat.com> (raw)
In-Reply-To: <1196314230.7950.42.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
Trond Myklebust wrote:
> Actually, the real problem would be dealing with something like
> unlink('foo') followed by open('foo', O_CREAT|O_EXCL). How do you ensure
> that a replay of those actions following a reboot is fully consistent in
> the face of some other client attempting an open('foo', O_CREAT) at the
> same time?
>
> The problem is that a number of directory operations involve exclusive
> semantics, and so cannot be replayed. The solution to this sort of
> problem is going to have to involve exclusive (i.e. write) directory
> delegations to ensure that whatever transactions one client performs
> cannot interfere with the transactions performed by another.
>
>
Well, a dumb question from me (borrowing Bruce's line :) ) ... even with
"sync" in place, when server rebooted, the RPC reply cache is gone. How
does linux server handle re-transmitted non-idempotent requests ?
-- Wendy
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
next prev parent reply other threads:[~2007-11-30 16:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.194659.1195581701.26582.nfs@lists.sourceforge.net>
2007-11-20 20:22 ` [NFS] NFS Digest, Vol 18, Issue 70 (NFS performance problems) Wendy Cheng
[not found] ` <BAY104-W43766F661E50E7FFCDA8EBA7F0-MsuGFMq8XAE@public.gmane.org>
2007-11-20 21:17 ` Peter Staubach
2007-11-20 21:23 ` Wendy Cheng
2007-11-21 16:04 ` Chuck Lever
2007-11-26 3:28 ` Wendy Cheng
2007-11-26 4:41 ` Trond Myklebust
2007-11-26 5:02 ` J. Bruce Fields
[not found] ` <18254.19187.470275.538680@notabene.brown>
[not found] ` <18254.19187.470275.538680-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2007-11-29 5:30 ` Trond Myklebust
[not found] ` <1196314230.7950.42.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2007-11-30 16:27 ` Wendy Cheng [this message]
2007-12-03 20:31 ` J. Bruce Fields
2007-12-03 21:13 ` Wendy Cheng
2007-12-03 21:30 ` J. Bruce Fields
2007-12-03 21:38 ` J. Bruce Fields
2007-12-03 21:49 ` Wendy Cheng
2007-12-03 22:07 ` J. Bruce Fields
2007-11-27 18:40 ` Rui Pedro Mendes Salgueiro
[not found] ` <20071127184050.GA13791-/uZbGGhPd8Gmv2Aub4FSgw@public.gmane.org>
2007-11-28 1:50 ` 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=475039E4.5070903@redhat.com \
--to=wcheng@redhat.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=neilb-YbfuJp6tym7X/JP9YwkgDA@public.gmane.org \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.