From: Alan Hagge <ahagge@wbfa.com>
To: linux-kernel@vger.kernel.org
Subject: NFS issue: Irix server, Linux client - inode number mismatch
Date: Fri, 12 Oct 2001 15:00:56 -0700 [thread overview]
Message-ID: <3BC76818.BA84A90E@wbfa.com> (raw)
We have an SGI Irix 6.5-based server running NFS3 with Linux 2.4.7
clients attaching. Whenever the server crashes, the Linux clients have
problems with their NFS mounts. Typically, they're unusable until after
reboot.
The /var/log/messages file on the Linux client side has the following
messages:
Oct 8 16:01:27 lrender2 automount[22485]: expired
/usr/local/sgi/wbfa
Oct 8 16:01:27 lrender2 kernel: nfs_refresh_inode: inode number
mismatch
Oct 8 16:01:27 lrender2 kernel: expected (0x3000007/0x6467c36),
got (0x3000005/0x6467c36)
Oct 8 16:06:27 lrender2 automount[22486]: expired
/usr/local/sgi/wbfa
Oct 8 16:06:27 lrender2 kernel: nfs_refresh_inode: inode number
mismatch
Oct 8 16:06:27 lrender2 kernel: expected (0x3000007/0x6467c36),
got (0x3000005/0x6467c36)
Oct 8 16:11:27 lrender2 automount[22487]: expired
/usr/local/sgi/wbfa
Oct 8 16:11:27 lrender2 kernel: nfs_refresh_inode: inode number
mismatch
Oct 8 16:11:27 lrender2 kernel: expected (0x3000007/0x6467c36),
got (0x3000005/0x6467c36)
Can anyone tell me if this is expected behavior, and if not, if the
problem is in the Irix NFS server implementation or the
Linux client implementation? I don't have the NFS expertise to be able
to discern...
BTW, other clients (SGI Irix and Mac OS X workstations) connected to the
same mount points do NOT exhibit this
behaviour after a server crash.
I checked the changelog at
http://www.fys.uio.no/~trondmy/src/ChangeLog.NFSv3 but didn't see
anything relevant.
Thanks,
Alan Hagge
Replies via cc:, please...
next reply other threads:[~2001-10-12 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-12 22:00 Alan Hagge [this message]
2001-10-13 18:29 ` NFS issue: Irix server, Linux client - inode number mismatch Trond Myklebust
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3BC76818.BA84A90E@wbfa.com \
--to=ahagge@wbfa.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.