All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Schillinger <mschilli@vss.fsi.com>
To: James Pearson <james-p@moving-picture.com>
Cc: 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: 19 Sep 2003 08:26:31 -0500	[thread overview]
Message-ID: <1063977995.2766.4.camel@mosix> (raw)
In-Reply-To: <3F6A21E1.9090404@moving-picture.com>

On Thu, 2003-09-18 at 16:21, James Pearson wrote:
> Chris Worley wrote:
> >
> > 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?
> 
> I don't know a lot about NFS fail over, but I guess unless the take-over 
> server has a copy (or the same copy) of /var/lib/nfs/rmtab, then you 
> will get "permission denied" - the server needs an entry for each 
> client. I guess it works some of the time as the take-over server has a 
> 'valid' entry in its rmtab file for that client.
>

Yes, i made a little daemon that for each exported directory, generates
a 'directory specific' rmtab file in
/path/to/directory/.nfs_cluster/rmtab. It updates each export directory
every 2 seconds and copies the rmtab to rmtab.old , then generates a
clean rmtab. it has worked fine for me to prevent permission
denied/Stale NFS handles.

Upon the failover, after the filesystem is mounted by the 'takeover
server', the .nfs_cluster/rmtab is processed and added to
/var/lib/nfs/rmtab before exportfs instances are ran on the export
directories.

What are you using for failover?

I use heartbeat.

I also had to make a 2 second delay after IP takeover, for the IP to
actually be working, before I run the exportfs for the newly mounted
filesystem.

Matt Schillinger
mschilli@vss.fsi.com

 
> James Pearson
> 
> 
> 
> -------------------------------------------------------
> 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





-------------------------------------------------------
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 13:24 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 [this message]
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
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=1063977995.2766.4.camel@mosix \
    --to=mschilli@vss.fsi.com \
    --cc=cworley@lnxi.com \
    --cc=james-p@moving-picture.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.