From: "Randy.Dunlap" <rddunlap@osdlab.org>
To: Adam McKenna <adam-dated-999656018.ee55e0@flounder.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Strange kernel messages
Date: Fri, 31 Aug 2001 08:22:15 -0700 [thread overview]
Message-ID: <3B8FABA7.D06F4ACF@osdlab.org> (raw)
In-Reply-To: <20010830191338.D19430@flounder.net>
Adam McKenna wrote:
>
> Can someone please explain what these error messages mean?
>
> Aug 30 12:23:17 ren kernel: expected (0x3af6c03f/0x24d6e80), got
> (0x3af6c03f/0x24d4ba0)
> Aug 30 12:23:17 ren kernel: expected (0x3af6c03f/0x24d4ba0), got
> (0x3af6c03f/0x24d6e80)
> Aug 30 12:35:02 ren kernel: expected (0x3af6c03f/0x24d6e80), got
> (0x3af6c03f/0x24d4ba0)
> Aug 30 12:35:02 ren kernel: expected (0x3af6c03f/0x24d4ba0), got
> (0x3af6c03f/0x24d6e80)
> Aug 30 13:49:36 ren kernel: expected (0x3af6c03f/0x2c05e81), got
> (0x3af6c03f/0x2c05ea0)
> Aug 30 13:49:36 ren kernel: expected (0x3af6c03f/0x2c05ea0), got
> (0x3af6c03f/0x2c05e81)
> Aug 30 13:54:38 ren kernel: expected (0x3af6c03f/0x2c05e81), got
> (0x3af6c03f/0x2c05ea0)
> Aug 30 13:54:38 ren kernel: expected (0x3af6c03f/0x2c05ea0), got
> (0x3af6c03f/0x2c05e81)
> Aug 30 13:59:40 ren kernel: expected (0x3af6c03f/0x2c05e81), got
> (0x3af6c03f/0x2c05ea0)
> Aug 30 13:59:40 ren kernel: expected (0x3af6c03f/0x2c05ea0), got
> (0x3af6c03f/0x2c05e81)
> Aug 30 14:04:41 ren kernel: expected (0x3af6c03f/0x2c05e81), got
> (0x3af6c03f/0x2c05ea0)
> Aug 30 14:04:41 ren kernel: expected (0x3af6c03f/0x2c05ea0), got
> (0x3af6c03f/0x2c05e81)
> Aug 30 14:09:43 ren kernel: expected (0x3af6c03f/0x2c05e81), got
> (0x3af6c03f/0x2c05ea0)
> Aug 30 14:09:43 ren kernel: expected (0x3af6c03f/0x2c05ea0), got
> (0x3af6c03f/0x2c05e81)
> Aug 30 14:10:19 ren kernel: expected (0x3af6c03f/0x2c05e81), got
> (0x3af6c03f/0x2c05ea0)
> Aug 30 14:10:19 ren kernel: expected (0x3af6c03f/0x2c05ea0), got
> (0x3af6c03f/0x2c05e81)
> Aug 30 14:15:17 ren kernel: expected (0x3af6c03f/0x2c05e81), got
> (0x3af6c03f/0x2c05ea0)
> Aug 30 14:15:17 ren kernel: expected (0x3af6c03f/0x2c05ea0), got
> (0x3af6c03f/0x2c05e81)
> Aug 30 14:20:19 ren kernel: expected (0x3af6c03f/0x2c05e81), got
> (0x3af6c03f/0x2c05ea0)
> Aug 30 14:20:19 ren kernel: expected (0x3af6c03f/0x2c05ea0), got
> (0x3af6c03f/0x2c05e81)
> Aug 30 14:25:21 ren kernel: expected (0x3af6c03f/0x2c05e81), got
> (0x3af6c03f/0x2c05ea0)
> Aug 30 14:25:21 ren kernel: expected (0x3af6c03f/0x2c05ea0), got
> (0x3af6c03f/0x2c05e81)
> Aug 30 14:30:23 ren kernel: expected (0x3af6c03f/0x2c05e81), got
> (0x3af6c03f/0x2c05ea0)
> Aug 30 14:30:23 ren kernel: expected (0x3af6c03f/0x2c05ea0), got
> (0x3af6c03f/0x2c05e81)
> Aug 30 14:35:27 ren kernel: expected (0x3af6c03f/0x2c05e81), got
> (0x3af6c03f/0x2c05ea0)
> Aug 30 14:35:27 ren kernel: expected (0x3af6c03f/0x2c05ea0), got
> (0x3af6c03f/0x2c05e81)
>
> This is on stock Linux 2.4.5, SMP enabled.
Couple of observations:
a. Not knowing this message, I grepped thru the kernel source tree
and found it easily (hint). It comes from linux/fs/nfs/inode.c,
when the NFS inode is being updated but doesn't match what is
expected (it seems, from reading the code and comments).
b. Some kernel message context would usually be helpful.
This message should have been preceded by the message:
nfs_refresh_inode: inode number mismatch
I expect that some FS/NFS people can give you even better info.
~Randy
prev parent reply other threads:[~2001-08-31 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-31 2:13 Strange kernel messages Adam McKenna
2001-08-31 15:22 ` Randy.Dunlap [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=3B8FABA7.D06F4ACF@osdlab.org \
--to=rddunlap@osdlab.org \
--cc=adam-dated-999656018.ee55e0@flounder.net \
--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