From: "Chris Carlson" <c.carlson@aristoslogic.com>
To: nfs@lists.sourceforge.net
Subject: Re: nfs_refresh_inode: inode number mismatch
Date: Thu, 27 Sep 2007 17:11:30 -0700 [thread overview]
Message-ID: <46FC46B2.2000800@aristoslogic.com> (raw)
In-Reply-To: <20070911130226.131bad3d.jlayton@redhat.com>
A few weeks ago, I asked for assistance in finding the cause for an
issue with NFS we were experiencing. The original message is below.
We followed a path down a response we received having to do with an old
version of the OnTap system on our NetApps servers. Apparently, it is a
caching problem that is known when using NetApps NFS servers.
Suddenly, we discovered the same problem with our Snap Appliance
servers. Now we can't blame it on NetApps.
A theory we came up with was that the real-time clock on our boards is
not operational. Is it possible that during our frequent reboots, the
sequence number of NFS RPC calls is coinciding with previous runs, and
the server is responding with cached packets having the same sequence
number on the previous run?
I have noticed that in Linux 2.4, the random seed appears to be
generated from the lower 16 bits of the MAC address. This implies to me
that it is quite likely the sequence numbers would be identical from one
run to the next.
Does our theory that the server is sending cached responses sound plausible?
Thanks for your time,
Chris
> On Tue, 11 Sep 2007 09:41:51 -0700
> "Chris Carlson" <c.carlson@aristoslogic.com> wrote:
>
>
>> We are running MontaVista Embedded Linux 2.4 with NetApps NFS servers as
>> the root filesystem and Linux 2.6 mounted filesystems. A simple test
>> runs to copy files from one mount point to another (both are different
>> directories on the same NFS server mounted at differet points).
>>
>> After 30 copies of a hundred files are made, the system is rebooted and
>> the test repeats.
>>
>> After 2 reboots, an NFS file is created, and we get the following error
>> from the kernel:
>>
>> nfs_refresh_inode: inode number mismatch
>> expected (0x11/0xdacea3), got (0x11/0xb8d5e3)
>>
>>
>
>
>
CONFIDENTIALITY NOTICE:
This email, together with any attachments, is intended only for use by Aristos Logic Corporation and the
individual(s) to which it is addressed and may contain information that is privileged, confidential or
exempt from disclosure. If you are not the intended recipient, you are hereby notified that any dissemination,
distribution, or copying of this email, or any attachment, is strictly prohibited. If you have received this
email in error, please notify Aristos Logic Corporation by sending an email to sysadm@aristoslogic.com
and delete this email, along with any attachments, from your computer.
Thank you.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-09-28 0:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- 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-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=46FC46B2.2000800@aristoslogic.com \
--to=c.carlson@aristoslogic.com \
--cc=nfs@lists.sourceforge.net \
/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.