From: Calum Mackay <calum.mackay@sun.com>
To: Marc Eshel <eshel@almaden.ibm.com>
Cc: "William A.(Andy) Adamson" <andros@citi.umich.edu>,
Neil Brown <neilb@cse.unsw.edu.au>,
nfs@lists.sourceforge.net, nfs-admin@lists.sourceforge.net,
Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: [patch] lockd control of grace period for HA NFS
Date: Wed, 01 Dec 2004 17:17:46 +0000 [thread overview]
Message-ID: <41ADFCBA.6040605@sun.com> (raw)
In-Reply-To: <OF7203D852.9E05A09B-ON88256F5C.005C4DD8-88256F5C.005DB624@us.ibm.com>
Hi Marc, Andy,
Forgive my late joining of this thread, and apologies if I'm missing
anything...
How do you intend to handle the stable storage issue? It seems to me
that to comply with the RFC's requirement that stable storage be used
when a grace period is offered, there needs to be a Cluster-wide,
always-consistent, stable-storage, available to all nodes. I imagine
that a correct implementation of this isn't a trivial exercise... :)
best regards,
calum.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-12-01 17:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16802.32693.974799.504191@cse.unsw.edu.au>
2004-11-24 3:38 ` [patch] lockd control of grace period for HA NFS Marc Eshel
2004-11-24 4:28 ` Trond Myklebust
2004-11-24 5:35 ` Marc Eshel
2004-11-24 16:21 ` Trond Myklebust
2004-11-24 23:49 ` Marc Eshel
2004-11-25 0:15 ` Trond Myklebust
2004-11-29 23:12 ` Marc Eshel
2004-11-30 15:55 ` William A.(Andy) Adamson
2004-11-30 17:03 ` Marc Eshel
2004-12-01 17:17 ` Calum Mackay [this message]
2004-12-01 20:58 ` William A.(Andy) Adamson
2004-12-06 15:04 ` J. Bruce Fields
2004-12-06 18:20 ` Marc Eshel
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=41ADFCBA.6040605@sun.com \
--to=calum.mackay@sun.com \
--cc=andros@citi.umich.edu \
--cc=eshel@almaden.ibm.com \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs-admin@lists.sourceforge.net \
--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.