From: Rashmi Agrawal <rashmi.agrawal@wipro.com>
To: linux-kernel@vger.kernel.org
Subject: Failover in NFS
Date: Mon, 18 Nov 2002 20:34:55 +0530 [thread overview]
Message-ID: <3DD90197.4DDEEE61@wipro.com> (raw)
Hi All,
I might be very wrong but I am trying to do following
1. I have a 4 node cluster and nfsv3 in all the nodes of cluster with
server running in one
of the 2 nodesconnected to shared storage and 2 other nodes are acting
as clients.
2. If nfs server node crashes, I need to failover to another node
wherein I need to have access
to the lock state of the previous server and I need to tell the clients
that the IP address of the
nfs server node has changed. IS IT POSSIBLE or what can be done to
implement it?
Another scenario is..
1. When one of the client crashes, it has to failover to another client,
in that case if client
crashed with some locks held how the newly come up client going to grab
the lock again
when it is not released? Again the server might already be taking care
of it but I am not
sure about it.
I hope I can use NFS for this kind of set up and if not what will it
take to have this kind of set
up usinf NFS?
Regards
Rashmi
next reply other threads:[~2002-11-18 14:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-18 15:04 Rashmi Agrawal [this message]
2002-11-18 15:44 ` Failover in NFS Ragnar Kjørstad
2002-11-18 22:11 ` Jesse Pollard
2002-11-18 22:22 ` Ragnar Kjørstad
2002-11-18 22:41 ` Jesse Pollard
2002-11-18 22:51 ` Ragnar Kjørstad
2002-11-19 1:36 ` Michael Clark
2002-11-19 5:07 ` Rashmi Agrawal
2002-11-19 7:40 ` Michael Clark
2002-11-22 7:07 ` Rashmi Agrawal
2002-11-21 20:58 ` Bill Davidsen
2002-11-21 22:52 ` Jesse Pollard
2002-11-22 19:19 ` Gunther Mayer
2002-11-18 22:33 ` Jan Niehusmann
-- strict thread matches above, loose matches on Subject: below --
2002-11-19 18:24 Juan Gomez
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=3DD90197.4DDEEE61@wipro.com \
--to=rashmi.agrawal@wipro.com \
--cc=linux-kernel@vger.kernel.org \
/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