From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Alan Hagge <ahagge@wbfa.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS issue: Irix server, Linux client - inode number mismatch
Date: 13 Oct 2001 20:29:51 +0200 [thread overview]
Message-ID: <shsbsjbs89s.fsf@charged.uio.no> (raw)
In-Reply-To: <3BC76818.BA84A90E@wbfa.com>
In-Reply-To: Alan Hagge's message of "Fri, 12 Oct 2001 15:00:56 -0700"
>>>>> " " == Alan Hagge <ahagge@wbfa.com> writes:
> /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)
That means that the device number or 'fsid' suddenly has changed on
your server. That's a server bug.
Cheers,
Trond
prev parent reply other threads:[~2001-10-13 18:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-12 22:00 NFS issue: Irix server, Linux client - inode number mismatch Alan Hagge
2001-10-13 18:29 ` Trond Myklebust [this message]
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=shsbsjbs89s.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox