His problems are likely more generic than just XFS / NFS integration.
NFS (on any filesystem) has not historically been very compatible with
fail-over clustering and gives the stale handle message after a fail-over.
As Horms said, there has been a lot of discussion and development related to
The heartbeat mailing lists archives should cover this topic in detail. (80+
messages at last count)
It requires a fair bit of effort, but it can be accomplished.
To my knowledge there is not a out-of-the-box solution, and neither is there a
nice clearly written how-to.
Deployment and Integration Specialist
Compaq ASE - Tru64
Compaq Master ASE - SAN Architect
The Norcross Group
>> hi Hugo -
>> Is there a chance that you could try the most recent CVS code? There
>> have been some changes in the way errors return out of xfs_lookup, which
>> has affected NFS in a few ways.
>> If CVS behaves better, but you'd prefer to run XFS 1.1, we can probably
>> come up with a patch for 1.1 for you.
>> On Tue, 2002-05-07 at 05:15, Hugo Lafargue wrote:
>> > But, I'm now observing that after failover, nfs clients are unable to
>> > the filesystem exported by the backup server until I unmount it and
>> > it again. Otherwise, I get "stale NFS file handle" messages.
>> Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs
>> sandeen@xxxxxxx SGI, Inc.