From mboxrd@z Thu Jan  1 00:00:00 1970
From: Eric Ford <oscar_install@yahoo.com>
Subject: nfs failover
Date: Sat, 10 Jan 2004 19:02:38 -0800 (PST)
Sender: nfs-admin@lists.sourceforge.net
Message-ID: <20040111030238.18638.qmail@web12607.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="0-191229932-1073790158=:18407"
Return-path: <nfs-admin@lists.sourceforge.net>
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.12] helo=sc8-sf-mx2.sourceforge.net)
	by sc8-sf-list2.sourceforge.net with esmtp (Exim 4.24)
	id 1AfVs6-0007Zn-TQ
	for nfs@lists.sourceforge.net; Sat, 10 Jan 2004 19:02:38 -0800
Received: from web12607.mail.yahoo.com ([216.136.173.230])
	by sc8-sf-mx2.sourceforge.net with smtp (Exim 4.30)
	id 1AfVs6-0006nJ-Ly
	for nfs@lists.sourceforge.net; Sat, 10 Jan 2004 19:02:38 -0800
To: nfs@lists.sourceforge.net
Errors-To: nfs-admin@lists.sourceforge.net
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/nfs>,
	<mailto:nfs-request@lists.sourceforge.net?subject=unsubscribe>
List-Id: Discussion of NFS under Linux development,
	interoperability,
	and testing. <nfs.lists.sourceforge.net>
List-Post: <mailto:nfs@lists.sourceforge.net>
List-Help: <mailto:nfs-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/nfs>,
	<mailto:nfs-request@lists.sourceforge.net?subject=subscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=nfs>

--0-191229932-1073790158=:18407
Content-Type: text/plain; charset=us-ascii

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
--0-191229932-1073790158=:18407
Content-Type: text/html; charset=us-ascii

<DIV>Hello, everybody</DIV>
<DIV>&nbsp;</DIV>
<DIV>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 </DIV>
<DIV>backup server&nbsp;has the same IP and hostname and same configuration at that time.</DIV>
<DIV>&nbsp;</DIV>
<DIV>"NFS server is not responding, still trying"&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>I use this command: #service nfs restart&nbsp;&nbsp;&nbsp; on backup server, it is not useful.</DIV>
<DIV>&nbsp;</DIV>
<DIV>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.</DIV>
<P>Thank you</P>
<P>Eric</P><p><hr SIZE=1>
Do you Yahoo!?<br>
Yahoo! Hotjobs: <a href="http://pa.yahoo.com/*http://us.rd.yahoo.com/hotjobs/mail_footer_email/evt=21482/*http://hotjobs.sweepstakes.yahoo.com/signingbonus">Enter the "Signing Bonus" Sweepstakes</a>
--0-191229932-1073790158=:18407--


-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

From mboxrd@z Thu Jan  1 00:00:00 1970
From: Brian Tinsley <btlists@emageon.com>
Subject: Re: nfs failover
Date: Sat, 10 Jan 2004 22:55:37 -0600
Sender: nfs-admin@lists.sourceforge.net
Message-ID: <1073796936.2771.18.camel@dragonball>
References: <20040111030238.18638.qmail@web12607.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=-u0IsBsyoNz+VGkOHp2lU"
Cc: nfs@lists.sourceforge.net
Return-path: <nfs-admin@lists.sourceforge.net>
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.12] helo=sc8-sf-mx2.sourceforge.net)
	by sc8-sf-list2.sourceforge.net with esmtp (Exim 4.24)
	id 1AfXde-0003QD-Ke
	for nfs@lists.sourceforge.net; Sat, 10 Jan 2004 20:55:50 -0800
Received: from [63.162.183.61] (helo=emgexg01.emgdom001.emageon.com)
	by sc8-sf-mx2.sourceforge.net with esmtp (Exim 4.30)
	id 1AfXde-0006dr-At
	for nfs@lists.sourceforge.net; Sat, 10 Jan 2004 20:55:50 -0800
To: Eric Ford <oscar_install@yahoo.com>
In-Reply-To: <20040111030238.18638.qmail@web12607.mail.yahoo.com>
Errors-To: nfs-admin@lists.sourceforge.net
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/nfs>,
	<mailto:nfs-request@lists.sourceforge.net?subject=unsubscribe>
List-Id: Discussion of NFS under Linux development,
	interoperability,
	and testing. <nfs.lists.sourceforge.net>
List-Post: <mailto:nfs@lists.sourceforge.net>
List-Help: <mailto:nfs-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/nfs>,
	<mailto:nfs-request@lists.sourceforge.net?subject=subscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=nfs>


--=-u0IsBsyoNz+VGkOHp2lU
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

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

--=-u0IsBsyoNz+VGkOHp2lU
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.0.8">
</HEAD>
<BODY>
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.<BR>
<BR>
<BR>
On Sat, 2004-01-10 at 21:02, Eric Ford wrote:
<BLOCKQUOTE TYPE=CITE>
    <FONT COLOR="#737373"><I>Hello, everybody<BR>
    &nbsp;<BR>
    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 <BR>
    backup server&nbsp;has the same IP and hostname and same configuration at that time.<BR>
    &nbsp;<BR>
    &quot;NFS server is not responding, still trying&quot;&nbsp;<BR>
    &nbsp;<BR>
    I use this command: #service nfs restart&nbsp;&nbsp;&nbsp; on backup server, it is not useful.<BR>
    &nbsp;<BR>
    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.<BR>
    <BR>
    Thank you<BR>
    <BR>
    Eric<BR>
    <BR>
    
<HR SIZE="1">
Do you Yahoo!?<BR>
    Yahoo! Hotjobs: </FONT><A HREF="http://pa.yahoo.com/*http://us.rd.yahoo.com/hotjobs/mail_footer_email/evt=21482/*http://hotjobs.sweepstakes.yahoo.com/signingbonus"><U>Enter the &quot;Signing Bonus&quot; Sweepstakes</U></I></A>
</BLOCKQUOTE>
</BODY>
</HTML>

--=-u0IsBsyoNz+VGkOHp2lU--



-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Saurabh Sehgal" <saurabh.r.s@gmail.com>
Subject: Re: Nfs Failover
Date: Wed, 10 Oct 2007 09:38:18 -0400
Message-ID: <2a46ebd60710100638k5665f025vbadb8d7194262f1a@mail.gmail.com>
References: <2a46ebd60710091240k37369e15rbc99b57d26579e8a@mail.gmail.com>
	<20071009195128.GQ22750@fieldses.org> <470BDFB9.30409@cesca.es>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1299659895=="
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	nfs@lists.sourceforge.net
To: "Jordi Prats" <jprats@cesca.es>
Return-path: <nfs-bounces@lists.sourceforge.net>
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1IfblR-0001lK-2C
	for nfs@lists.sourceforge.net; Wed, 10 Oct 2007 06:38:17 -0700
Received: from mu-out-0910.google.com ([209.85.134.188])
	by mail.sourceforge.net with esmtp (Exim 4.44) id 1IfblV-0000KE-Ly
	for nfs@lists.sourceforge.net; Wed, 10 Oct 2007 06:38:22 -0700
Received: by mu-out-0910.google.com with SMTP id w9so235664mue
	for <nfs@lists.sourceforge.net>; Wed, 10 Oct 2007 06:38:20 -0700 (PDT)
In-Reply-To: <470BDFB9.30409@cesca.es>
List-Id: "Discussion of NFS under Linux development, interoperability,
	and testing." <nfs.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/nfs>,
	<mailto:nfs-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=nfs>
List-Post: <mailto:nfs@lists.sourceforge.net>
List-Help: <mailto:nfs-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/nfs>,
	<mailto:nfs-request@lists.sourceforge.net?subject=subscribe>
Sender: nfs-bounces@lists.sourceforge.net
Errors-To: nfs-bounces@lists.sourceforge.net

--===============1299659895==
Content-Type: multipart/alternative;
	boundary="----=_Part_12003_18989059.1192023498946"

------=_Part_12003_18989059.1192023498946
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,

I will be sure to try that and see if I get the same problem ...

I am exporting an ext3 filesystem ... Does that change anything ?

Thank you,

Saurabh

On 10/9/07, Jordi Prats <jprats@cesca.es> wrote:
>
> To avoid the stale state on your clients you should add a tag to your
> exported filesystems. For example:
>
> /usr 10.0.0.1(rw,sync,no_root_squash,nohide,fsid=1)
> /usr 10.0.0.2(rw,sync,no_root_squash,nohide,fsid=1)
>
> /var 10.0.0.1(rw,sync,no_root_squash,nohide,fsid=2)
> /var 10.0.0.2(rw,sync,no_root_squash,nohide,fsid=2)
>
> regards,
> Jordi
>
> J. Bruce Fields wrote:
> > On Tue, Oct 09, 2007 at 03:40:22PM -0400, Saurabh Sehgal wrote:
> >> Hi all,
> >>
> >> I am trying to do an nfs failover from one server to another in a 4
> node
> >> cluster . During this failover, I have a link from /var/lib/nfs
> directory to
> >> a mount that resides on a shared disk. When i want to move the
> "resources"
> >> from one node to the other ... this is how I go about initiating the
> move :
> >>
> >> 1) /etc/init.d/nfsserver stop
> >> 2) mount /var/lib/nfs on the failover node
> >> 3) move IP address to failover node
> >> 3) /etc/init.d/nfsserver start
> >> 4) /sbin/sm-notify -v <failover ip address>
> >>
> >> Are these the correct steps ? What I end up getting is a Stale NFS File
> >> handle on all client nodes, until I unmount and remount them again. For
> the
> >> purpose of my application this mount/unmount of clients is undesirable
> .
> >> What should I do ? Any help would be appreciated.
> >
> > What filesystem are you exporting?
> >
> > --b.
> >
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > _______________________________________________
> > NFS maillist  -  NFS@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nfs
> >
> >
>

------=_Part_12003_18989059.1192023498946
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi, <br><br>I will be sure to try that and see if I get the same problem ...<br><br>I am exporting an ext3 filesystem ... Does that change anything ?<br><br>Thank you, <br><br>Saurabh<br><br><div><span class="gmail_quote">
On 10/9/07, <b class="gmail_sendername">Jordi Prats</b> &lt;<a href="mailto:jprats@cesca.es">jprats@cesca.es</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
To avoid the stale state on your clients you should add a tag to your<br>exported filesystems. For example:<br><br>/usr 10.0.0.1(rw,sync,no_root_squash,nohide,fsid=1)<br>/usr 10.0.0.2(rw,sync,no_root_squash,nohide,fsid=1)
<br><br>/var 10.0.0.1(rw,sync,no_root_squash,nohide,fsid=2)<br>/var 10.0.0.2(rw,sync,no_root_squash,nohide,fsid=2)<br><br>regards,<br>Jordi<br><br>J. Bruce Fields wrote:<br>&gt; On Tue, Oct 09, 2007 at 03:40:22PM -0400, Saurabh Sehgal wrote:
<br>&gt;&gt; Hi all,<br>&gt;&gt;<br>&gt;&gt; I am trying to do an nfs failover from one server to another in a 4 node<br>&gt;&gt; cluster . During this failover, I have a link from /var/lib/nfs directory to<br>&gt;&gt; a mount that resides on a shared disk. When i want to move the &quot;resources&quot;
<br>&gt;&gt; from one node to the other ... this is how I go about initiating the move :<br>&gt;&gt;<br>&gt;&gt; 1) /etc/init.d/nfsserver stop<br>&gt;&gt; 2) mount /var/lib/nfs on the failover node<br>&gt;&gt; 3) move IP address to failover node
<br>&gt;&gt; 3) /etc/init.d/nfsserver start<br>&gt;&gt; 4) /sbin/sm-notify -v &lt;failover ip address&gt;<br>&gt;&gt;<br>&gt;&gt; Are these the correct steps ? What I end up getting is a Stale NFS File<br>&gt;&gt; handle on all client nodes, until I unmount and remount them again. For the
<br>&gt;&gt; purpose of my application this mount/unmount of clients is undesirable .<br>&gt;&gt; What should I do ? Any help would be appreciated.<br>&gt;<br>&gt; What filesystem are you exporting?<br>&gt;<br>&gt; --b.<br>
&gt;<br>&gt; -------------------------------------------------------------------------<br>&gt; This SF.net email is sponsored by: Splunk Inc.<br>&gt; Still grepping through log files to find problems?&nbsp;&nbsp;Stop.<br>&gt; Now Search log events and configuration files using AJAX and a browser.
<br>&gt; Download your FREE copy of Splunk now &gt;&gt; <a href="http://get.splunk.com/">http://get.splunk.com/</a><br>&gt; _______________________________________________<br>&gt; NFS maillist&nbsp;&nbsp;-&nbsp;&nbsp;<a href="mailto:NFS@lists.sourceforge.net">
NFS@lists.sourceforge.net</a><br>&gt; <a href="https://lists.sourceforge.net/lists/listinfo/nfs">https://lists.sourceforge.net/lists/listinfo/nfs</a><br>&gt;<br>&gt;<br></blockquote></div><br>

------=_Part_12003_18989059.1192023498946--


--===============1299659895==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
--===============1299659895==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

--===============1299659895==--

From mboxrd@z Thu Jan  1 00:00:00 1970
From: "J. Bruce Fields" <bfields@fieldses.org>
Subject: Re: Nfs Failover
Date: Wed, 10 Oct 2007 09:40:54 -0400
Message-ID: <20071010134054.GA31732@fieldses.org>
References: <2a46ebd60710091240k37369e15rbc99b57d26579e8a@mail.gmail.com>
	<20071009195128.GQ22750@fieldses.org> <470BDFB9.30409@cesca.es>
	<2a46ebd60710100638k5665f025vbadb8d7194262f1a@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: nfs@lists.sourceforge.net
To: Saurabh Sehgal <saurabh.r.s@gmail.com>
Return-path: <nfs-bounces@lists.sourceforge.net>
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1Ifbo3-0001yv-HG
	for nfs@lists.sourceforge.net; Wed, 10 Oct 2007 06:40:59 -0700
Received: from mail.fieldses.org ([66.93.2.214] helo=fieldses.org)
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1Ifbo6-00066x-II
	for nfs@lists.sourceforge.net; Wed, 10 Oct 2007 06:41:04 -0700
In-Reply-To: <2a46ebd60710100638k5665f025vbadb8d7194262f1a@mail.gmail.com>
List-Id: "Discussion of NFS under Linux development, interoperability,
	and testing." <nfs.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/nfs>,
	<mailto:nfs-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=nfs>
List-Post: <mailto:nfs@lists.sourceforge.net>
List-Help: <mailto:nfs-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/nfs>,
	<mailto:nfs-request@lists.sourceforge.net?subject=subscribe>
Sender: nfs-bounces@lists.sourceforge.net
Errors-To: nfs-bounces@lists.sourceforge.net

On Wed, Oct 10, 2007 at 09:38:18AM -0400, Saurabh Sehgal wrote:
> I will be sure to try that and see if I get the same problem ...
> 
> I am exporting an ext3 filesystem ...

So you're using a shared block device?

> Does that change anything ?

It's just important to make sure you're exporting the *identical* ext3
filesystem from the two servers--copies made above the filesystem level
(using cp or rsync or whatever) aren't sufficient to ensure that
filehandles stay the same.

--b.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Saurabh Sehgal" <saurabh.r.s@gmail.com>
Subject: Nfs Failover
Date: Tue, 9 Oct 2007 15:40:22 -0400
Message-ID: <2a46ebd60710091240k37369e15rbc99b57d26579e8a@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1798326725=="
To: nfs@lists.sourceforge.net
Return-path: <nfs-bounces@lists.sourceforge.net>
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1IfKwG-00081B-El
	for nfs@lists.sourceforge.net; Tue, 09 Oct 2007 12:40:20 -0700
Received: from fk-out-0910.google.com ([209.85.128.185])
	by mail.sourceforge.net with esmtp (Exim 4.44) id 1IfKwK-0004Ix-ED
	for nfs@lists.sourceforge.net; Tue, 09 Oct 2007 12:40:25 -0700
Received: by fk-out-0910.google.com with SMTP id 19so1644177fkr
	for <nfs@lists.sourceforge.net>; Tue, 09 Oct 2007 12:40:23 -0700 (PDT)
List-Id: "Discussion of NFS under Linux development, interoperability,
	and testing." <nfs.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/nfs>,
	<mailto:nfs-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=nfs>
List-Post: <mailto:nfs@lists.sourceforge.net>
List-Help: <mailto:nfs-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/nfs>,
	<mailto:nfs-request@lists.sourceforge.net?subject=subscribe>
Sender: nfs-bounces@lists.sourceforge.net
Errors-To: nfs-bounces@lists.sourceforge.net

--===============1798326725==
Content-Type: multipart/alternative;
	boundary="----=_Part_7665_15546596.1191958822817"

------=_Part_7665_15546596.1191958822817
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi all,

I am trying to do an nfs failover from one server to another in a 4 node
cluster . During this failover, I have a link from /var/lib/nfs directory to
a mount that resides on a shared disk. When i want to move the "resources"
from one node to the other ... this is how I go about initiating the move :

1) /etc/init.d/nfsserver stop
2) mount /var/lib/nfs on the failover node
3) move IP address to failover node
3) /etc/init.d/nfsserver start
4) /sbin/sm-notify -v <failover ip address>

Are these the correct steps ? What I end up getting is a Stale NFS File
handle on all client nodes, until I unmount and remount them again. For the
purpose of my application this mount/unmount of clients is undesirable .
What should I do ? Any help would be appreciated.

( I am using SLES 10 SP 1 as a platform :
uname -a
Linux mach1 2.6.16.46-0.12-smp #1 SMP Thu May 17 14:00:09 UTC 2007 x86_64
x86_64 x86_64 GNU/Linux  )


Thank you,

Saurabh

------=_Part_7665_15546596.1191958822817
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi all, <br><br>I am trying to do an nfs failover from one server to another in a 4 node cluster . During this failover, I have a link from /var/lib/nfs directory to a mount that resides on a shared disk. When i want to move the &quot;resources&quot; from one node to the other ... this is how I go about initiating the move :
<br><br>1) /etc/init.d/nfsserver stop<br>2) mount /var/lib/nfs on the failover node<br>3) move IP address to failover node<br>3) /etc/init.d/nfsserver start<br>4) /sbin/sm-notify -v &lt;failover ip address&gt;<br><br>Are these the correct steps ? What I end up getting is a Stale NFS File handle on all client nodes, until I unmount and remount them again. For the purpose of my application this mount/unmount of clients is undesirable . What should I do ? Any help would be appreciated.
<br><br>( I am using SLES 10 SP 1 as a platform :<br>uname -a<br>Linux mach1 2.6.16.46-0.12-smp #1 SMP Thu May 17 14:00:09 UTC 2007 x86_64 x86_64 x86_64 GNU/Linux&nbsp; )<br><br><br>Thank you, <br><br>Saurabh<br>

------=_Part_7665_15546596.1191958822817--


--===============1798326725==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
--===============1798326725==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

--===============1798326725==--

From mboxrd@z Thu Jan  1 00:00:00 1970
From: "J. Bruce Fields" <bfields@fieldses.org>
Subject: Re: Nfs Failover
Date: Tue, 9 Oct 2007 15:51:28 -0400
Message-ID: <20071009195128.GQ22750@fieldses.org>
References: <2a46ebd60710091240k37369e15rbc99b57d26579e8a@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: nfs@lists.sourceforge.net
To: Saurabh Sehgal <saurabh.r.s@gmail.com>
Return-path: <nfs-bounces@lists.sourceforge.net>
Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1IfL70-0000iy-HM
	for nfs@lists.sourceforge.net; Tue, 09 Oct 2007 12:51:26 -0700
Received: from mail.fieldses.org ([66.93.2.214] helo=fieldses.org)
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1IfL74-0007mP-F3
	for nfs@lists.sourceforge.net; Tue, 09 Oct 2007 12:51:31 -0700
In-Reply-To: <2a46ebd60710091240k37369e15rbc99b57d26579e8a@mail.gmail.com>
List-Id: "Discussion of NFS under Linux development, interoperability,
	and testing." <nfs.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/nfs>,
	<mailto:nfs-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=nfs>
List-Post: <mailto:nfs@lists.sourceforge.net>
List-Help: <mailto:nfs-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/nfs>,
	<mailto:nfs-request@lists.sourceforge.net?subject=subscribe>
Sender: nfs-bounces@lists.sourceforge.net
Errors-To: nfs-bounces@lists.sourceforge.net

On Tue, Oct 09, 2007 at 03:40:22PM -0400, Saurabh Sehgal wrote:
> Hi all,
> 
> I am trying to do an nfs failover from one server to another in a 4 node
> cluster . During this failover, I have a link from /var/lib/nfs directory to
> a mount that resides on a shared disk. When i want to move the "resources"
> from one node to the other ... this is how I go about initiating the move :
> 
> 1) /etc/init.d/nfsserver stop
> 2) mount /var/lib/nfs on the failover node
> 3) move IP address to failover node
> 3) /etc/init.d/nfsserver start
> 4) /sbin/sm-notify -v <failover ip address>
> 
> Are these the correct steps ? What I end up getting is a Stale NFS File
> handle on all client nodes, until I unmount and remount them again. For the
> purpose of my application this mount/unmount of clients is undesirable .
> What should I do ? Any help would be appreciated.

What filesystem are you exporting?

--b.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jordi Prats <jprats@cesca.es>
Subject: Re: Nfs Failover
Date: Tue, 09 Oct 2007 22:08:25 +0200
Message-ID: <470BDFB9.30409@cesca.es>
References: <2a46ebd60710091240k37369e15rbc99b57d26579e8a@mail.gmail.com>
	<20071009195128.GQ22750@fieldses.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: nfs@lists.sourceforge.net
To: "J. Bruce Fields" <bfields@fieldses.org>
Return-path: <nfs-bounces@lists.sourceforge.net>
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1IfLGA-0001ik-7S
	for nfs@lists.sourceforge.net; Tue, 09 Oct 2007 13:00:54 -0700
Received: from carlit.cesca.es ([84.88.0.2])
	by mail.sourceforge.net with esmtps (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.44) id 1IfLGB-00036K-2L
	for nfs@lists.sourceforge.net; Tue, 09 Oct 2007 13:00:59 -0700
In-Reply-To: <20071009195128.GQ22750@fieldses.org>
List-Id: "Discussion of NFS under Linux development, interoperability,
	and testing." <nfs.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/nfs>,
	<mailto:nfs-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=nfs>
List-Post: <mailto:nfs@lists.sourceforge.net>
List-Help: <mailto:nfs-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/nfs>,
	<mailto:nfs-request@lists.sourceforge.net?subject=subscribe>
Sender: nfs-bounces@lists.sourceforge.net
Errors-To: nfs-bounces@lists.sourceforge.net

To avoid the stale state on your clients you should add a tag to your 
exported filesystems. For example:

/usr 10.0.0.1(rw,sync,no_root_squash,nohide,fsid=1)
/usr 10.0.0.2(rw,sync,no_root_squash,nohide,fsid=1)

/var 10.0.0.1(rw,sync,no_root_squash,nohide,fsid=2)
/var 10.0.0.2(rw,sync,no_root_squash,nohide,fsid=2)

regards,
Jordi

J. Bruce Fields wrote:
> On Tue, Oct 09, 2007 at 03:40:22PM -0400, Saurabh Sehgal wrote:
>> Hi all,
>>
>> I am trying to do an nfs failover from one server to another in a 4 node
>> cluster . During this failover, I have a link from /var/lib/nfs directory to
>> a mount that resides on a shared disk. When i want to move the "resources"
>> from one node to the other ... this is how I go about initiating the move :
>>
>> 1) /etc/init.d/nfsserver stop
>> 2) mount /var/lib/nfs on the failover node
>> 3) move IP address to failover node
>> 3) /etc/init.d/nfsserver start
>> 4) /sbin/sm-notify -v <failover ip address>
>>
>> Are these the correct steps ? What I end up getting is a Stale NFS File
>> handle on all client nodes, until I unmount and remount them again. For the
>> purpose of my application this mount/unmount of clients is undesirable .
>> What should I do ? Any help would be appreciated.
> 
> What filesystem are you exporting?
> 
> --b.
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> NFS maillist  -  NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
> 
> 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs