From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Birger Lammering <b.lammering@science-computing.de>
Cc: linux-kernel@vger.kernel.org
Subject: nfs problem: hp|aix-server --- linux 2.4.15pre5 client
Date: Fri, 16 Nov 2001 12:45:41 +0100 [thread overview]
Message-ID: <15348.64613.465429.628445@charged.uio.no> (raw)
In-Reply-To: <15348.63313.961267.735216@stderr.science-computing.de>
In-Reply-To: <20011115222920.A9929@ludwig2.science-computing.de> <shssnbf37td.fsf@charged.uio.no> <15348.63313.961267.735216@stderr.science-computing.de>
>>>>> " " == Birger Lammering <b.lammering@science-computing.de> writes:
> not reproduce the Ooops with the HP nfs server. But still: The
> Kernel complains about: "NFS: short packet in readdir reply!"
> when I access any directory provided by a HP-UX 10.20
> nfs-server (using nfs2 | nfs3). I dont' notice any strange
> behaviour other than that, though.
That's because the HP is returning a READDIR reply that is larger than
the buffer size we specified. When this happens, we truncate the reply
at the last valid record before the buffer overflow, and print out the
above message.
> But a new problem emerged: Copying from a linux (2.4.13 |
> 2.4.15pre5) nfs-client onto an AIX nfs-server doesn't
> work. About 800kb are copied then the cp command just
> hangs. Syslog says: Nov 16 11:51:12 capc20 kernel: nfs: server
> caes04 not responding, still trying This problem only occures
> with nfs3, and not with nfs2.
> Is there a cure for this, without being too experimental?
No idea. That depends on where the problem lies...
Do you have a tcpdump for me? Preferably one from the client and one
from the server (showing the same period of time).
Cheers,
Trond
next prev parent reply other threads:[~2001-11-16 11:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15349.39320.876188.274548@charged.uio.no>
2001-11-15 21:29 ` nfs problem: hp-server --- linux 2.4.13 client, ooops Birger Lammering
2001-11-15 23:58 ` Trond Myklebust
2001-11-16 11:45 ` Trond Myklebust [this message]
2001-11-16 12:01 ` nfs problem: hp|aix-server --- linux 2.4.15pre5 client Miquel van Smoorenburg
2001-11-16 12:24 ` Trond Myklebust
2001-11-16 11:24 ` Birger Lammering
2001-11-16 13:19 ` nfs problem: aix-server " Birger Lammering
2001-11-19 10:20 ` IPV4 socket layer, was: " Birger Lammering
2001-11-19 11:16 ` Alan Cox
2001-11-19 18:22 ` more tcpdumpinfo for nfs3 " Trond Myklebust
2001-11-19 18:49 ` kuznet
2001-11-19 18:55 ` Trond Myklebust
2001-11-19 19:09 ` kuznet
2001-11-19 19:29 ` Trond Myklebust
2001-11-19 19:52 ` kuznet
2001-11-19 20:38 ` Trond Myklebust
2001-11-19 21:17 ` Trond Myklebust
2001-11-20 17:42 ` kuznet
2001-11-20 19:39 ` Trond Myklebust
2001-11-20 19:45 ` kuznet
2001-11-20 20:29 ` Trond Myklebust
2001-11-21 10:07 ` Trond Myklebust
2001-11-21 17:05 ` kuznet
2001-11-20 20:05 ` Trond Myklebust
2001-11-20 20:18 ` David S. Miller
2001-11-20 20:28 ` more tcpdumpinfo for nfs3 problem: aix-server --- linux kuznet
2001-11-20 17:41 ` more tcpdumpinfo for nfs3 problem: aix-server --- linux 2.4.15pre5 client kuznet
2001-11-19 16:37 ` Birger Lammering
2001-11-20 9:26 ` Birger Lammering
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=15348.64613.465429.628445@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=b.lammering@science-computing.de \
--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
all inboxes | Powered by JetHome®