From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Zdravko Spoljar" <flirek@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nfs_refresh_inode ?
Date: 27 Feb 2001 21:36:59 +0100 [thread overview]
Message-ID: <shsy9urhnh0.fsf@charged.uio.no> (raw)
In-Reply-To: <LAW2-F2101vraQ4yvco00012ad0@hotmail.com>
In-Reply-To: "Zdravko Spoljar"'s message of "Tue, 27 Feb 2001 18:34:24 -0000"
>>>>> " " == Zdravko Spoljar <flirek@hotmail.com> writes:
> Hi i'm running 2.2.19pre14+RAID+ide and get this message from
> kernel:
> nfs_refresh_inode: inode number mismatch expected
> (0x0ffffffff/0x0ffffffff), got (0x0002b0001/0x00005605)
> ^^^^
Could you get a tcpdump of a the traffic when this happens? I suspect
a server bug.
> marked numbers vary from message to message. i can triger this
> by doing "make test;chmod 777 test" on some nfs mounted file
> sistem some times repeated chmod generate more messages,
> sometimes are executed ok. i have feeling it happend more often
> when there is some cpu and net load.
> linux nfs client is dual pentium II (266) on P2B-DS with 2
> promise IDE cards, net card is smc (using realtek 8139 driver),
> ide and scsi disks are in RAID 5 setup.
> nfs server is Apple Network server running AIX4.1.5 net conn is
> 100MB over Cisco switch
> ah, there is one more thing. on boot when nfs get mounted i
> find in dmesg: "nfs warning: mount version older than kernel"
> WTF? :)
It means that your 'mount' program is too old, and so you won't be
able to mount NFSv3 partitions.
Cheers,
Trond
prev parent reply other threads:[~2001-02-27 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 18:34 nfs_refresh_inode ? Zdravko Spoljar
2001-02-27 20:36 ` Trond Myklebust [this message]
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=shsy9urhnh0.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=flirek@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
/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).