From: Bernd Schubert <bernd-schubert@gmx.de>
Subject: Re: Stale nfs file handle - cwd without path - workaround?
Date: Tue, 17 Jan 2006 00:43:17 +0100
Message-ID: <200601170043.18048.bernd-schubert@gmx.de>
References: <1137402966.3299.251938119@webmail.messagingengine.com>
Mime-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
To: nfs@lists.sourceforge.net,
	"Wally Winchester" <wally_winchester@fastmail.fm>
In-Reply-To: <1137402966.3299.251938119@webmail.messagingengine.com>
Sender: nfs-admin@lists.sourceforge.net
Errors-To: nfs-admin@lists.sourceforge.net

Hello Wally,

> When nfs1 dies, and nfs2 takes over, everything works - as long as the
> clients are writing files using the full paths.
> If the path is omitted, i.e. they are expecting a write to their cwd, a
> "stale nfs file handle" warning is issued.
>
> Is there a way around this?
>
> e.g. this works
> touch /nfs-mount/file
> (failover)
> touch /nfs-mount/file
>
> e.g. this doesn't work
> cd /nfs-mount/
> touch file
> (failover)
> touch file
> (stale nfs file handle)

really strange, we never had this problem. I think you have to provide some 
more information (/etc/exports of both servers, kernel version, distribution, 
how you handle /var/lib/nfs, drbd? configuration, etc.).

Cheers,
	Bernd


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs