** Reply to note from adp [EMAIL PROTECTED] Mon, 31 May 2004 12:33:24 -0500
I was thinking that
since NFS is udp-based, that if the primary NFS server failed, and the
secondary assumed the primary NFS server's IP address, that things would at
least return to normal (of course, any writes
On Sun, May 30, 2004 at 02:43:37AM -0500, adp wrote:
I am running a FreeBSD 4.9-REL NFS server. Once every several hours our main
NFS server replicates everything to a backup FreeBSD NFS server. We are okay
with the gap in time between replication. What we aren't sure about is how
to automate
adp wrote:
One of my big problems right now is that if our primary NFS server goes down
then everything using that NFS mount locks up. If I change to the mounted
filesystem on the client then it stalls:
# pwd
/root
# cd /nfs-mount-dir
[locks]
If I try to reboot the reboot fails as well since
We can live with the chance that a file write might fail as long as we can
switch over to another NFS server if the primary fails. So amd will help us
avoid the client hung issue? I will have to take a look. That is the worst
thing of all when it comes to a failed NFS server. You can't even
-
From: Chuck Swiger [EMAIL PROTECTED]
To: adp [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, May 31, 2004 11:55 AM
Subject: Re: NFS server fail-over - how do you do it?
adp wrote:
One of my big problems right now is that if our primary NFS server goes
down
then everything using
adp wrote:
We can live with the chance that a file write might fail as long as we can
switch over to another NFS server if the primary fails.
Sorry, NFS simply won't work with the model of operation you've described.
There is no way to do fallback to a secondary NFS server if the primary goes
In the last episode (May 31), adp said:
Very useful information, thanks. We have a very stable NFS server,
but I am still working hard to put some redundancy into place. I was
thinking that since NFS is udp-based, that if the primary NFS server
failed, and the secondary assumed the primary NFS
Couple of issues regarding failover.
1) If system B is going to take over system a's IP,
it also needs to take it's MAC address. Else you
have to wait for an ARP timeout.
Some systems (all?) perform a gratuitous arp-reply
when an if comes up. But some other systems ignore
this
On Sun, 30 May 2004 02:43:37 -0500
adp [EMAIL PROTECTED] wrote:
I am running a FreeBSD 4.9-REL NFS server. Once every several hours our main
NFS server replicates everything to a backup FreeBSD NFS server. We are okay
with the gap in time between replication. What we aren't sure about is how
On Sun, 30 May 2004 02:43:37 -0500
adp [EMAIL PROTECTED] wrote:
Just curious how this problem is being solved.
I cant say i've ever looked into it myself but id susjest an easy solution would be to
have a cron script store run every now and again to ping the servers and change the
mounts
One of my big problems right now is that if our primary NFS server goes down
then everything using that NFS mount locks up. If I change to the mounted
filesystem on the client then it stalls:
# pwd
/root
# cd /nfs-mount-dir
[locks]
If I try to reboot the reboot fails as well since FreeBSD can't
11 matches
Mail list logo
