On Wed, Jun 04, 2003 at 04:19:38PM +0200, Trond Myklebust wrote:
> >>>>> " " == Frank Cusack <fcusack@fcusack.com> writes:
> > 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().
Clearly it's not the former. No way a netapp filer is going to have
this problem. I can't imagine *any* nfs server having this problem.
Could you take another look at the specific case I cited? At the time
I try to access the file, the path to it no longer exists. No information
on this file should exist.
/fc
-
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 : Sat Jun 07 2003 - 22:00:25 EST