![]() | |||||||||||||
Messages in this thread |
On Wed, 4 Jun 2003 14:20:47 -0700 "Frank Cusack" <fcusack@fcusack.com> wrote: > 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(). There's a very common cause on embedded boards that don't have real-time clocks. Without a clock the client uses the same XID on every run, leading to lots of these messages. Is your clock broken? - Adrian Cox http://www.humboldt.co.uk/ - 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 12:36 [from the cache] ©2003-2008 | |||||||||||||