?
Solved

NFS replication & Failover errors

Posted on 2008-10-28
2
Medium Priority
?
672 Views
Last Modified: 2013-12-27
Hi All,

We have been having this problem with NFS failover.  Today we suffered an issue which caused our clients to failover to the secondary NFS server.  Every time this happens, we get these warnings

Oct 28 10:09:24 web47t nfs: [ID 694808 kern.notice] NOTICE: NFS: failing over from nas1 to nfs2
Oct 28 10:09:24 web47t nfs: [ID 442997 kern.warning] WARNING: NFS replicas nas1 and nfs2: file ./indexes not same.
Oct 28 10:09:24 web47t nfs: [ID 442997 kern.warning] WARNING: NFS replicas nas1 and nfs2: file ./features/common/moth not same.
Oct 28 10:09:24 web47t nfs: [ID 694808 kern.notice] NOTICE: NFS: failing over from nfs2 to nas1
Oct 28 10:09:24 web47t nfs: [ID 442997 kern.warning] WARNING: NFS replicas nfs2 and nas1: file ./indexes not same.
Oct 28 10:09:24 web47t nfs: [ID 442997 kern.warning] WARNING: NFS replicas nfs2 and nas1: file ./slideshow/2008 not same.
Oct 28 10:09:24 web47t nfs: [ID 442997 kern.warning] WARNING: NFS replicas nfs2 and nas1: file ./weather/data not same.
Oct 28 10:09:24 web47t nfs: [ID 694808 kern.notice] NOTICE: NFS: failing over from nas1 to nfs2
Oct 28 10:09:24 web47t nfs: [ID 442997 kern.warning] WARNING: NFS replicas nas1 and nfs2: file ./indexes not same.
Oct 28 10:09:24 web47t nfs: [ID 442997 kern.warning] WARNING: NFS replicas nas1 and nfs2: file ./weather not same.
Oct 28 10:09:24 web47t nfs: [ID 442997 kern.warning] WARNING: NFS replicas nas1 and nfs2: file ./indexes/2008 not same.

The files are read-only and they are the same... is there some checksuming file or state file that could be cleared out during a failover?  

Any ideas why NFS thinks they are not the same files?
Were running Solaris 10 X86
nas1 is a EMC/Dell Clarion CX-600
0
Comment
Question by:jedblack
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 22

Accepted Solution

by:
blu earned 1500 total points
ID: 22822863
This message is printed when the type and size of the files do not match.
0
 
LVL 1

Author Comment

by:jedblack
ID: 22941706
yes...i know that, but the file ARE the same.. doing checksum's and they are exactly the same...size/mod date/checksum

and other ideas?

thanks

0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When you do backups in the Solaris Operating System, the file system must be inactive. Otherwise, the output may be inconsistent. A file system is inactive when it's unmounted or it's write-locked by the operating system. Although the fssnap utility…
I promised to write further about my project, and here I am.  First, I needed to setup the Primary Server.  You can read how in this article: Setup FreeBSD Server with full HDD encryption (http://www.experts-exchange.com/OS/Unix/BSD/FreeBSD/A_3660-S…
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
Learn how to navigate the file tree with the shell. Use pwd to print the current working directory: Use ls to list a directory's contents: Use cd to change to a new directory: Use wildcards instead of typing out long directory names: Use ../ to move…
Suggested Courses

718 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question