From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Wendy Cheng <wcheng@redhat.com>
Cc: cluster-devel@redhat.com, lhh@redhat.com,
Linux NFS Mailing List <nfs@lists.sourceforge.net>,
Greg Banks <gnb@melbourne.sgi.com>
Subject: Re: [PATCH 0/3] NLM lock failover
Date: Fri, 04 Aug 2006 11:51:48 -0400 [thread overview]
Message-ID: <1154706709.4727.21.camel@localhost> (raw)
In-Reply-To: <1154703362.3378.45.camel@localhost.localdomain>
On Fri, 2006-08-04 at 10:56 -0400, Wendy Cheng wrote:
> Anyway, better be conservative than sorry - I think we want to switch to
> "fsid" approach to avoid messing with these networking issues, including
> IPV6 modification. That is, we use fsid as the key to drop the lock and
> set per-fsid NLM grace period. The ha-callout will have a 4th argument
> (fsid) when invoked.
What is the point of doing that? As far as the client is concerned, a
server has either rebooted or it hasn't. It doesn't know about single
filesystems rebooting.
Cheers,
Trond
-------------------------------------------------------------------------
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:[~2006-08-04 15:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 17:47 [RFC PATCH 0/3] NLM lock failover Wendy Cheng
2006-08-01 1:55 ` [PATCH " Wendy Cheng
2006-08-03 4:14 ` Neil Brown
2006-08-04 9:27 ` Greg Banks
2006-08-04 13:27 ` Wendy Cheng
2006-08-04 14:56 ` Wendy Cheng
2006-08-04 15:51 ` Trond Myklebust [this message]
2006-08-05 5:44 ` Wendy Cheng
2006-08-07 4:05 ` Greg Banks
2006-08-07 20:14 ` James Yarbrough
2006-08-07 4:05 ` Greg Banks
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=1154706709.4727.21.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=cluster-devel@redhat.com \
--cc=gnb@melbourne.sgi.com \
--cc=lhh@redhat.com \
--cc=nfs@lists.sourceforge.net \
--cc=wcheng@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox