All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd-schubert@web.de>
To: Chris Worley <cworley@lnxi.com>, nfs@lists.sourceforge.net
Subject: Re: Stopping NFS, ip address take over, zero-copy NFS for 2.4.21, and misc
Date: Fri, 19 Sep 2003 14:50:24 +0200	[thread overview]
Message-ID: <200309191450.24184.bernd-schubert@web.de> (raw)
In-Reply-To: <1063900790.8031.9644.camel@localhost.localdomain>

> 2) IP address takeover between NFS servers.
>
> With NFS stateless, and not running lock servers, I thought a simple IP
> address takeover scheme (when an I/O server goes down, another just adds
> the failed server's IP address as a virtual interface) would allow
> clients to immediately renegotiate with the same IP address pointing to
> another NFS server (serving the same partitions).  The take-over is
> successful: the clients can communicate with the new I/O server, but I
> get "permission denied" (as root or otherwise) on the NFS mounted
> partitions most of the time (sometimes it works).
>
> What am I missing?
>

Don't know whats going wrong at your network, but it works pretty well on o=
ur=20
systems.=20
How do you sync both server system (main server and fall back server)? Well=
,=20
since its here a root-fs server and changes are done rarely, we simply=20
connect them via nbd and sync using dd of the whole device once a night.
=46or our main-data server (/home, etc) there is currently no fall back, bu=
t we=20
plan to doing this in the near future. To do so, we want to connect via enb=
d=20
and do a network raid1 between both systems.=20
Let me guess, do you sync using tar, etc.? This won't work since you need t=
he=20
very same inode numbers. The only way to do so, is to use network raid or a=
=20
1:1 copy of the whole partion-device.

Cheers,
	Bernd


Bernd Schubert
Physikalisch Chemisches Institut / Theoretische Chemie
Universit=E4t Heidelberg
INF 229
69120 Heidelberg
e-mail: bernd.schubert@pci.uni-heidelberg.de


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  parent reply	other threads:[~2003-09-19 12:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-18 15:59 Stopping NFS, ip address take over, zero-copy NFS for 2.4.21, and misc Chris Worley
2003-09-18 21:21 ` James Pearson
2003-09-19  1:11   ` Chris Worley
2003-09-19 13:26   ` Matt Schillinger
2003-09-19 22:41     ` Chris Worley
2003-09-19  9:04 ` rnews
2003-09-20 10:22   ` An NFS-HA HOWTO anyone? WAS> " ian sison (mailing list)
2003-09-22 14:24     ` Matt Schillinger
2003-09-19 12:50 ` Bernd Schubert [this message]
2003-09-19 15:35 ` rnews

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=200309191450.24184.bernd-schubert@web.de \
    --to=bernd-schubert@web.de \
    --cc=cworley@lnxi.com \
    --cc=nfs@lists.sourceforge.net \
    /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.