From: Frank Cusack <fcusack@fcusack.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: nfs_refresh_inode: inode number mismatch
Date: Wed, 4 Jun 2003 14:20:47 -0700 [thread overview]
Message-ID: <20030604142047.C24603@google.com> (raw)
In-Reply-To: <shswug2sz5x.fsf@charged.uio.no>; from trond.myklebust@fys.uio.no on Wed, Jun 04, 2003 at 04:19:38PM +0200
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
next prev parent reply other threads:[~2003-06-04 21:07 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 23:54 nfs_refresh_inode: inode number mismatch Frank Cusack
2003-06-04 14:19 ` Trond Myklebust
2003-06-04 21:20 ` Frank Cusack [this message]
2003-06-04 21:28 ` Trond Myklebust
2003-06-05 9:11 ` Adrian Cox
2003-06-05 9:13 ` Russell King
2003-06-05 13:51 ` Trond Myklebust
2003-06-09 13:51 ` [PATCH] nfs_unlink() race (was: nfs_refresh_inode: inode number mismatch) Frank Cusack
2003-06-09 13:55 ` Frank Cusack
2003-06-09 15:53 ` Linus Torvalds
2003-06-09 16:40 ` Trond Myklebust
2003-06-09 20:46 ` Frank Cusack
2003-06-10 0:01 ` Trond Myklebust
2003-06-11 0:54 ` viro
2003-06-11 1:28 ` Frank Cusack
2003-06-11 1:47 ` viro
2003-06-11 2:32 ` Frank Cusack
2003-06-11 2:37 ` viro
2003-06-11 1:59 ` Trond Myklebust
2003-06-11 2:27 ` viro
2003-06-11 2:43 ` Frank Cusack
2003-06-11 2:50 ` Frank Cusack
2003-06-11 3:00 ` viro
2003-06-11 7:22 ` [PATCH] NFS sillyrename fixes (was: [PATCH] nfs_unlink() race) Frank Cusack
2003-06-13 0:19 ` [PATCH] NFS sillyrename fixes take 3 Frank Cusack
2003-06-11 3:00 ` [PATCH] nfs_unlink() race (was: nfs_refresh_inode: inode number mismatch) Trond Myklebust
2003-06-11 5:30 ` Linus Torvalds
2003-06-11 6:16 ` Andreas Dilger
2003-06-11 12:33 ` Alan Cox
2003-06-11 15:08 ` Linus Torvalds
2003-06-11 15:51 ` Alan Cox
2003-06-11 16:11 ` Linus Torvalds
2003-06-11 16:21 ` Alan Cox
2003-06-11 16:31 ` Linus Torvalds
2003-06-11 16:34 ` viro
2003-06-11 17:22 ` Alan Cox
2003-06-11 17:37 ` Trond Myklebust
2003-06-11 17:47 ` Trond Myklebust
2003-06-12 21:59 ` Jan Harkes
[not found] ` <16103.29804.198545.680701@charged.uio.no>
2003-06-11 22:24 ` Frank Cusack
2003-06-11 23:16 ` Trond Myklebust
2003-06-11 23:35 ` [PATCH] nfs_unlink() race Frank Cusack
-- strict thread matches above, loose matches on Subject: below --
2007-09-11 16:41 nfs_refresh_inode: inode number mismatch Chris Carlson
2007-09-11 17:02 ` Jeff Layton
2007-09-11 17:43 ` Jeff Layton
2007-09-11 21:11 ` Chris Carlson
2007-09-28 0:11 ` Chris Carlson
2007-09-28 14:52 ` Chuck Lever
2007-09-11 17:09 ` Chuck Lever
2007-09-11 21:15 ` Chris Carlson
2007-09-21 20:46 ` Trond Myklebust
2001-07-17 0:24 Marco d'Itri
2001-07-17 9:44 ` Trond Myklebust
2001-07-18 22:25 ` Marco d'Itri
2001-07-19 11:00 ` Trond Myklebust
2001-02-22 22:30 Scott A McConnell
2001-02-22 21:59 ` Russell King
2001-02-23 9:30 ` Trond Myklebust
2001-02-08 1:13 Jun Sun
2001-02-08 1:22 ` Neil Brown
2001-02-08 8:08 ` Russell King
2001-02-09 0:02 ` Jun Sun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030604142047.C24603@google.com \
--to=fcusack@fcusack.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.