* inode number mismatch message
@ 2002-04-04 8:28 Kent, Ian I.
2002-04-04 9:04 ` James Pearson
0 siblings, 1 reply; 2+ messages in thread
From: Kent, Ian I. @ 2002-04-04 8:28 UTC (permalink / raw)
To: 'nfs@lists.sourceforge.net'
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: inode number mismatch message
2002-04-04 8:28 inode number mismatch message Kent, Ian I.
@ 2002-04-04 9:04 ` James Pearson
0 siblings, 0 replies; 2+ messages in thread
From: James Pearson @ 2002-04-04 9:04 UTC (permalink / raw)
To: Kent, Ian I.; +Cc: nfs
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-04-04 9:04 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-04-04 8:28 inode number mismatch message Kent, Ian I.
2002-04-04 9:04 ` James Pearson
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.