From: Scott A McConnell <samcconn@cotw.com>
To: linux-kernel@vger.kernel.org
Subject: nfs_refresh_inode: inode number mismatch
Date: Thu, 22 Feb 2001 14:30:12 -0800 [thread overview]
Message-ID: <3A9592F4.FFCC2236@cotw.com> (raw)
I am getting NFS errors/warnings
VFS: Mounted root (nfs filesystem).
Freeing unused kernel memory: 196k freed
nfs_refresh_inode: inode number mismatch
expected (0x806/0x6246a), got (0x806/0x62b48)
^/var/run/utmp
^/var/log/wtmp **************
nfs_refresh_inode: inode number mismatch
expected (0x806/0x62b48), got (0x806/0x6246a)
nfs_refresh_inode: inode number mismatch
expected (0x806/0x6246a), got (0x806/0x62b48)
nfs_refresh_inode: inode number mismatch
expected (0x806/0x62b4f), got (0x806/0x6246a)
^/var/run/inetd.pid
*****************
nfs_refresh_inode: inode number mismatch
expected (0x806/0x6246a), got (0x806/0x62b48)
nfs_refresh_inode: inode number mismatch
expected (0x806/0x62b48), got (0x806/0x6246a)
nfs_refresh_inode: inode number mismatch
expected (0x806/0x62b48), got (0x806/0x6246a)
nfs_refresh_inode: inode number mismatch
expected (0x806/0x6246a), got (0x806/0x62b48)
nfs_refresh_inode: inode number mismatch
expected (0x806/0x42d60), got (0x806/0x42d5f)
nfs_refresh_inode: inode number mismatch
expected (0x806/0x6246a), got (0x806/0x62b48)
nfs_refresh_inode: inode number mismatch
expected (0x806/0x6246a), got (0x806/0x62b48)
nfs_refresh_inode: inode number mismatch
expected (0x806/0x6246a), got (0x806/0x62b48)
I am running RedHat Linux version 2.2.16-3 on my PC and Hardhat Linux
version 2.4.0-test5 on my MIPS board. Any thoughts or suggestions?
I saw a discussion start on the ARM list along these lines but I never
saw a solution.
Please CC me at samcconn@cotw.com
Thanks,
Scott
next reply other threads:[~2001-02-22 20:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-22 22:30 Scott A McConnell [this message]
2001-02-22 21:59 ` nfs_refresh_inode: inode number mismatch Russell King
2001-02-23 9:30 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2007-09-11 16:41 Chris Carlson
2007-09-11 17:02 ` Jeff Layton
2007-09-11 17:43 ` Jeff Layton
2007-09-11 21:11 ` Chris Carlson
2007-09-28 0:11 ` Chris Carlson
2007-09-28 14:52 ` Chuck Lever
2007-09-11 17:09 ` Chuck Lever
2007-09-11 21:15 ` Chris Carlson
2007-09-21 20:46 ` Trond Myklebust
2003-06-03 23:54 Frank Cusack
2003-06-04 14:19 ` Trond Myklebust
2003-06-04 21:20 ` Frank Cusack
2003-06-04 21:28 ` Trond Myklebust
2003-06-05 9:11 ` Adrian Cox
2003-06-05 9:13 ` Russell King
2003-06-05 13:51 ` Trond Myklebust
2001-07-17 0:24 Marco d'Itri
2001-07-17 9:44 ` Trond Myklebust
2001-07-18 22:25 ` Marco d'Itri
2001-07-19 11:00 ` Trond Myklebust
2001-02-08 1:13 Jun Sun
2001-02-08 1:22 ` Neil Brown
2001-02-08 8:08 ` Russell King
2001-02-09 0:02 ` Jun Sun
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=3A9592F4.FFCC2236@cotw.com \
--to=samcconn@cotw.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.