From: "J. Bruce Fields" <bfields@fieldses.org>
To: Neil Brown <neilb@suse.de>
Cc: nfs@lists.sourceforge.net, Steve Dickson <SteveD@redhat.com>,
richterd@citi.umich.edu
Subject: Re: HEADS-UP: nearing nfs-utils 1.1.0 and statd changes.
Date: Fri, 16 Mar 2007 14:10:47 -0400 [thread overview]
Message-ID: <20070316181047.GD4538@fieldses.org> (raw)
In-Reply-To: <17914.20117.186786.830574@notabene.brown>
On Fri, Mar 16, 2007 at 07:00:21PM +1100, Neil Brown wrote:
> Statd currently does several very different things.
> 1/ It listens for monitor requests from lockd and creates
> files in /var/lib/nfs/sm/HOST
> 2/ It listens for notifications from peers and tells lockd
> that those peers have restarted.
> 3/ It moves files from sm/ to sm.bak/ and then tries to
> notify every host listed in sm.bak/
>
> The first is very similar to what NFSv4 needs for state management,
> though is somewhat simpler. I would like to create a better
> interface for the kernel to ask for state to be stored, and then use
> if for NFSv4 and NLM, subsuming this function.
NFSv4 needs something like the third as well--knfsd needs to know on
startup the list of clients that will be allowed to reclaim state from a
previous boot instance. (This is to protect clients that *think*
they're still holding locks on the server, but (thanks to a network
partition) don't realize that the server has actually rebooted twice.)
--b.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-03-16 18:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 8:00 HEADS-UP: nearing nfs-utils 1.1.0 and statd changes Neil Brown
2007-03-16 12:59 ` Talpey, Thomas
2007-03-18 23:02 ` Neil Brown
2007-03-19 18:40 ` Talpey, Thomas
2007-03-22 4:54 ` Neil Brown
2007-03-22 12:36 ` Talpey, Thomas
2007-03-16 14:03 ` Steve Dickson
2007-03-16 14:30 ` Kevin Coffman
2007-03-18 22:52 ` Neil Brown
2007-03-16 18:10 ` J. Bruce Fields [this message]
2007-03-18 23:49 ` Neil Brown
2007-03-19 23:02 ` J. Bruce Fields
2007-03-20 0:30 ` Talpey, Thomas
2007-03-20 1:14 ` J. Bruce Fields
2007-03-20 10:47 ` Talpey, Thomas
2007-03-20 11:24 ` William A. (Andy) Adamson
2007-03-20 14:26 ` J. Bruce Fields
2007-03-20 14:49 ` Talpey, Thomas
2007-03-20 14:57 ` J. Bruce Fields
2007-03-20 15:03 ` Talpey, Thomas
2007-03-20 12:32 ` Steve Dickson
2007-03-22 4:30 ` Neil Brown
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=20070316181047.GD4538@fieldses.org \
--to=bfields@fieldses.org \
--cc=SteveD@redhat.com \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=richterd@citi.umich.edu \
/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