lkml.org 
[lkml]   [2003]   [Jun]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: nfs_refresh_inode: inode number mismatch
From
Date
>>>>> " " == Frank Cusack <fcusack@fcusack.com> writes:

> Hi, [Previously sent to nfs@sourceforge with no response]

> I'm using a frankenstein kernel, 2.4.21-rc3 with some -ac bits,
> and 2.5.69 NFS+RPC backported to it. Like the CITI kernel (for
> krb5), but a little more aggressive on the bits backported.
> For the purpose of this email, I think the code I have
> questions with is similar or even identical from
> 2.4.21->2.5.69. I can reproduce this problem on a RH
> 2.4.20-9smp kernel.

> Consider these two shells running on the same machine:

> 1 2

> cd /nfs cd /nfs mkdir t echo foo > t/foo less t/foo
> [less waits for input]
> rm -rf t
> 'v'
> [vi tries to access tmp/foo]

> At this point, fs/nfs/inode.c:__nfs_refresh_inode() prints the
> "inode number mismatch" error. AFAICT, this is just noise, but
> the noise is driving me crazy. :-)

Inode number mismatch points to either an an obvious server error (it
is not providing unique filehandles) or corruption of the fattr struct
that was passed to nfs_refresh_inode().

Cheers,
Trond
-
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/

\
 
 \ /
  Last update: 2005-03-22 13:36    [W:0.086 / U:1.344 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site