From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Stefan Frank <sfr@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.18pre3-ac2 : stuck when mounting NFS v3 via automounter
Date: 27 Jan 2002 15:10:29 +0100 [thread overview]
Message-ID: <shsy9ij7ulm.fsf@charged.uio.no> (raw)
In-Reply-To: <20020126225232.GA1017@obelix.gallien.de>
In-Reply-To: <20020126225232.GA1017@obelix.gallien.de>
>>>>> " " == Stefan Frank <sfr@gmx.net> writes:
> Jan 23 13:06:47 asterix kernel: NFS: server cheating in read
> reply:
> count 270336 > recvd 8680
> Jan 12 22:36:47 asterix kernel: call_verify: server accept
> status: 2
> Jan 13 12:43:49 asterix kernel: expected (0x808/0x1c0b6), got
> (0x4000000040808/0x400000001c0b6)
> Anyone can tell me what they mean?
Those are all reports of server bugs.
The first says that you are receiving read packets that are reported
to be longer than they actually are. This is harmless, since the RPC
layer automatically truncates any packets that threaten to overflow
our buffers.
The second is a report from the RPC layer. The server is saying that
you are trying to use an RPC service that it doesn't support.
The third states that your server is returning seriously screwed up
file attributes: even the fileid (a.k.a. inode number) is changed.
None of the above errors can cause a client to hang, however I suggest
that you try upgrading/patching your server.
Cheers,
Trond
prev parent reply other threads:[~2002-01-27 14:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-26 22:52 Stefan Frank
2002-01-27 14:10 ` 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=shsy9ij7ulm.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome