From: Jun Sun <jsun@mvista.com>
To: linux-kernel@vger.kernel.org
Subject: nfs_refresh_inode: inode number mismatch
Date: Wed, 07 Feb 2001 17:13:10 -0800 [thread overview]
Message-ID: <3A81F2A6.DC5AB40B@mvista.com> (raw)
This is a weird problem that I am looking at right. It seems to indicate a
bug in the nfs server.
I have a MIPS machine that boots from a NFS root fs hosted on a redhat 6.2
workstation. Everything works fine except that after a few reboots I start to
see the error messages like the following:
Freeing unused kernel memory: 24k freed
INIT: version 2.77 booting
nfs_refresh_inode: inode number mismatch
expected (0x308/0x28b3d2), got (0x308/0x12b91b)
INIT: Entering runlevel: 3
sh-2.03#
Restarting the nfs server on the host does not get rid of the messages.
Things will get better if I reboot the host.
I traced the network packets, and it seems obvious that the server is
returning wrong fileid in the "write reply" message. Below is a segment of
the extracted packet trace. It is obvious that the nfs server returns a wrong
fileid for the same handle it returned earlier to the client. The confusing
part is the nfs server actually serves the first write request, and a couple
of other requests, correctly but failed for the second time, returning a wrong
fileid.
In my particular setup, it seems only certain files (inodes) tend to get
screwed up.
Does anybody have an idea as to what is wrong here?
Please cc your reply to my email address. TIA.
Jun
------------------
round 3:
case 1:
2177 lookup:
ioctl.save
2178 lookup reply:
fileid: 2667474
handle:
cabaebfed2b32800e6ab2800080300000803000054c21100b2302b0c00000000
2181 write:
offset:0
total count: 60
handle:
cabaebfed2b32800e6ab2800080300000803000054c21100b2302b0c00000000
2182 write reply:
fileid: 2667474
size: 60
2183 setattr:
handle:
cabaebfed2b32800e6ab2800080300000803000054c21100b2302b0c00000000
2184 setattr reply:
fileid: 2667474
2185 write:
handle:
cabaebfed2b32800e6ab2800080300000803000054c21100b2302b0c00000000
2186 write reply:
fileid 1227035
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-02-08 1:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 1:13 Jun Sun [this message]
2001-02-08 1:22 ` nfs_refresh_inode: inode number mismatch Neil Brown
2001-02-08 8:08 ` Russell King
2001-02-09 0:02 ` Jun Sun
2001-02-22 22:30 Scott A McConnell
2001-02-22 21:59 ` Russell King
2001-02-23 9:30 ` 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
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
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=3A81F2A6.DC5AB40B@mvista.com \
--to=jsun@mvista.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;
as well as URLs for NNTP newsgroup(s).