2001-02-22 20:28:56

by Scott A McConnell

[permalink] [raw]
Subject: nfs_refresh_inode: inode number mismatch

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 [email protected]

Thanks,
Scott



2001-02-22 22:03:39

by Russell King

[permalink] [raw]
Subject: Re: nfs_refresh_inode: inode number mismatch

Scott A McConnell writes:
> 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.

The problem is partly caused by the NFS server indefinitely caching NFS
request XIDs to responses, and the NFS client not having a way to generate
a random initial XID. (thus, for each reboot, it starts at the same XID
number).

Upgrade your NFS server to kernel 2.2.18, and don't reboot more than once
in a 2 minute window.

--
Russell King ([email protected]) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html

2001-02-23 09:31:23

by Trond Myklebust

[permalink] [raw]
Subject: Re: nfs_refresh_inode: inode number mismatch

>>>>> " " == Russell King <[email protected]> writes:

> Scott A McConnell writes:
>> 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.

> The problem is partly caused by the NFS server indefinitely
> caching NFS request XIDs to responses, and the NFS client not
> having a way to generate a random initial XID. (thus, for each
> reboot, it starts at the same XID number).

That shouldn't be true in the latest kernels. knfsd should normally
cache requests for no longer than 2 minutes with the changes made by
Neil following your bugreport.

Cheers,
Trond