I have a similar problem with the stale file handles. In my exports
file I do have the fsid option set:
/var/nfs/ 192.168.1.0/255.255.255.0(rw,sync,all_squash,fsid=1)
But after fail over to the other NFS server, I still get the stale file
handles error.
I don't know if it makes a difference, but I only use heartbeat to
control the VIPs, not the NFS server. Also, I'm exporting a directory
on the main file system, not a separate disk mounted just for NFS exports.
Ideas? Everything I've read said the fsid should take care of it.
This is on Fedora 8.
Thanks!
Kelly
Wayne Carty wrote:
Hey Guys,
I know this issue has been addressed in the forums but could not find a
solution that solve the issue with the clients throwing nfs stale file
handles when it fails over.
I am using SUSE 10.1 with OCFS running on my shared disks. I moved
/var/lib/nfs over to the share disk. I am using heartbeat v2 to manage the
ip fail over and the starting up of the nfs server. The shared disk is
mounted on both node. Both nodes are connected to my EMC shared storage. I
was wondering how to solve this problem using heartbeat V2. I have seen some
post where they talk about using iptables when the ip fails over. Any help
with this issue would be appreciated.
--
--------------------------------------------
-- Kelly Corbin
-- Network Administrator
--
-- http://www.theiqgroup.com
--
-- The IQ Group, Inc.
-- 11460 S. Hunter Dr.
-- Olathe, KS 66061
-- (913)-722-6700 x105
-- Fax 866-714-7282
--------------------------------------------
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
