From: Brian Tinsley <btlists@emageon.com>
To: Eric Ford <oscar_install@yahoo.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: nfs failover
Date: Sat, 10 Jan 2004 22:55:37 -0600 [thread overview]
Message-ID: <1073796936.2771.18.camel@dragonball> (raw)
In-Reply-To: <20040111030238.18638.qmail@web12607.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1297 bytes --]
There are some specific events that must occur in order to make NFS
server failover happen. You should search the mailing list archives for
the linux-ha software (a.k.a., heartbeat) for further details. NFS
server failover has been detailed there quite extensively over the past
couple of years. And if you do not use linux-ha for clustering
(especially in the context you describe here), I suggest you give it a
try.
On Sat, 2004-01-10 at 21:02, Eric Ford wrote:
> Hello, everybody
>
> I installed nfs on my cluster system, two head nodes(one is primary
> and another is backup) with two clients. They use NFS to store and
> transfer data between server and clients. But whenever failover
> happens, the client can't connect to backup server although
> backup server has the same IP and hostname and same configuration at
> that time.
>
> "NFS server is not responding, still trying"
>
> I use this command: #service nfs restart on backup server, it is
> not useful.
>
> What should I do on backup server so that client can get connection
> with it? By the way I use Pfilter (iptables) on both servers.
>
> Thank you
>
> Eric
>
>
> ______________________________________________________________________
> Do you Yahoo!?
> Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
[-- Attachment #2: Type: text/html, Size: 1851 bytes --]
next prev parent reply other threads:[~2004-01-11 4:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-11 3:02 nfs failover Eric Ford
2004-01-11 4:55 ` Brian Tinsley [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-09 19:40 Nfs Failover Saurabh Sehgal
2007-10-09 19:51 ` J. Bruce Fields
2007-10-09 20:08 ` Jordi Prats
2007-10-10 13:38 ` Saurabh Sehgal
2007-10-10 13:40 ` J. Bruce Fields
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=1073796936.2771.18.camel@dragonball \
--to=btlists@emageon.com \
--cc=nfs@lists.sourceforge.net \
--cc=oscar_install@yahoo.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 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.