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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Aug 31 2001 - 21:00:34 EST