From: "Marco d'Itri" <md@Linux.IT>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nfs_refresh_inode: inode number mismatch
Date: Thu, 19 Jul 2001 00:25:20 +0200 [thread overview]
Message-ID: <20010719002520.A5112@wonderland.linux.it> (raw)
In-Reply-To: <shsd76zsxd2.fsf@charged.uio.no>
On Jul 17, Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
> > 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
No, the kernel is plain unpatched 2.4.5.
>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...
Anything specific I can tell to their tech support?
Can I ignore these messages or I risk data corruption?
--
ciao,
Marco
next prev parent reply other threads:[~2001-07-18 23:16 UTC|newest]
Thread overview: 18+ 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
2001-07-18 22:25 ` Marco d'Itri [this message]
2001-07-19 11:00 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
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=20010719002520.A5112@wonderland.linux.it \
--to=md@linux.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).