Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 16 Nov 2001 06:24:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 16 Nov 2001 06:24:18 -0500 Received: from noc1.BelWue.de ([129.143.2.1]:37100 "EHLO noc1.BelWue.DE") by vger.kernel.org with ESMTP id ; Fri, 16 Nov 2001 06:24:05 -0500 From: Birger Lammering Message-ID: <15348.63313.961267.735216@stderr.science-computing.de> Date: Fri, 16 Nov 2001 12:24:01 +0100 To: Trond Myklebust CC: linux-kernel@vger.kernel.org Subject: nfs problem: hp|aix-server --- linux 2.4.15pre5 client In-Reply-To: In-Reply-To: <20011115222920.A9929@ludwig2.science-computing.de> X-Mailer: VM 6.89 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Mime-Version: 1.0 (generated by tm-edit 1.7) Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi Trond, Trond Myklebust writes: > > [] > > That particular Oops should already be fixed in 2.4.14. Thanks, I've tried 2.4.15pre5 (+ seekdir patch) now and could 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. 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? Cheers, Birger ps: It seems to be quite difficult to get (and surely to write :-) nfs3-clients that work with all thinkable other platforms - we not only have nfs problems with Linux-clients in out network... > > Cheers, > Trond > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/