From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Marco d'Itri" <md@Linux.IT>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nfs_refresh_inode: inode number mismatch
Date: 17 Jul 2001 11:44:57 +0200 [thread overview]
Message-ID: <shsd76zsxd2.fsf@charged.uio.no> (raw)
In-Reply-To: <20010717022405.A22156@wonderland.linux.it>
In-Reply-To: Marco d'Itri's message of "Tue, 17 Jul 2001 02:24:05 +0200"
>>>>> " " == Marco d'Itri <md@Linux.IT> writes:
> Jul 18 00:15:07 newsserver kernel: nfs_refresh_inode: inode
> number mismatch Jul 18 00:15:07 newsserver kernel: expected
> (0x3b30ac75/0x48d5), got (0x3b30ac75/0x8d04)
> I've got a flood of these messages while talking to a procom
> NAS this. Should I worry? Upgrade/patch the kernel? Yell at
> procom tech support?
Have you applied any extra patches to NFS? I remember one of my
patches (availalble from my WWW-page, but clearly marked experimental)
was generating these messages gratuitously.
If, on the other hand, you're using a clean kernel, I'd look into what
the server is doing. It sounds like it's doing the same thing that the
userland `nfs-server' does: namely to recycle filehandles after a file
gets deleted...
Cheers,
Trond
next prev parent reply other threads:[~2001-07-17 9:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-17 0:24 nfs_refresh_inode: inode number mismatch Marco d'Itri
2001-07-17 9:44 ` Trond Myklebust [this message]
2001-07-18 22:25 ` Marco d'Itri
2001-07-19 11:00 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2007-09-11 16:41 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
2003-06-03 23:54 Frank Cusack
2003-06-04 14:19 ` Trond Myklebust
2003-06-04 21:20 ` Frank Cusack
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
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=shsd76zsxd2.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=md@Linux.IT \
/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.