From: James Pearson <james-p@moving-picture.com>
To: "Kent, Ian I." <Ian.Kent@woodside.com.au>
Cc: nfs@lists.sourceforge.net
Subject: Re: inode number mismatch message
Date: Thu, 04 Apr 2002 10:04:40 +0100 [thread overview]
Message-ID: <3CAC1728.F07F4EBD@moving-picture.com> (raw)
In-Reply-To: 62D26CC4CB1CD3118EAA00805FBB65FA0B8B900E@perm01.woodside.com.au
A previous message from Trond had a workaround:
http://marc.theaimsgroup.com/?l=linux-nfs&m=101316526524213&w=2
I believe this change is in Trond's 2.4.18 patches ...
James Pearson
"Kent, Ian I." wrote:
>
> I recently got a rash of messages like these in the logs on our Linux
> clients:
>
> Mar 24 04:02:00 csl024 syslogd 1.4-0: restart.
> Mar 24 04:02:00 csl024 syslogd 1.4-0: restart.
> Mar 24 23:50:13 csl024 kernel: nfs: server perseus is not responding
> Mar 24 23:50:28 csl024 kernel: nfs: server perseus OK
> Mar 24 23:51:43 csl024 kernel: nfs_refresh_inode: inode number mismatch
> Mar 24 23:51:43 csl024 kernel: expected (0x2813c6d/0x4), got
> (0xa000013c6d/0x4)
> Mar 24 23:51:43 csl024 kernel: nfs_refresh_inode: inode number mismatch
> Mar 24 23:51:43 csl024 kernel: expected (0x2813c69/0x4), got
> (0xa000013c69/0x4)
> Mar 24 23:52:58 csl024 kernel: nfs_refresh_inode: inode number mismatch
> Mar 24 23:52:58 csl024 kernel: expected (0x2813c6d/0x4), got
> (0xa000013c6d/0x4)
> Mar 24 23:52:58 csl024 kernel: nfs_refresh_inode: inode number mismatch
> Mar 24 23:52:58 csl024 kernel: expected (0x2813c69/0x4), got
> (0xa000013c69/0x4)
>
> They appeared after the server (Solaris) to which the Linux (2.4.17 kernel
> with Tronds' patches) was upgraded from 2.6 to 2.8 while there were active
> mounts.
>
> I know it's a big ask to expect the client to be OK though such an activity,
> but the comment is 'the Solaris clients were OK after the upgrade'.
>
> I would appreciate an feedback on whether this is something that should
> fixable or not.
>
> Regards
> Ian Kent
>
> _______________________________________________
> NFS maillist - NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2002-04-04 9:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-04 8:28 inode number mismatch message Kent, Ian I.
2002-04-04 9:04 ` James Pearson [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=3CAC1728.F07F4EBD@moving-picture.com \
--to=james-p@moving-picture.com \
--cc=Ian.Kent@woodside.com.au \
--cc=nfs@lists.sourceforge.net \
/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.