From owner-freebsd-current Wed Oct 24 10:30: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtpzilla3.xs4all.nl (smtpzilla3.xs4all.nl [194.109.127.139]) by hub.freebsd.org (Postfix) with ESMTP id 7F3D737B409 for ; Wed, 24 Oct 2001 10:29:54 -0700 (PDT) Received: from trantor.xs4all.nl (trantor.xs4all.nl [194.109.61.248]) by smtpzilla3.xs4all.nl (8.12.0/8.12.0) with ESMTP id f9OHUvt8043829; Wed, 24 Oct 2001 19:31:03 +0200 (CEST) Received: from trantor.xs4all.nl (localhost [127.0.0.1]) by trantor.xs4all.nl (8.11.6/8.9.3) with ESMTP id f9OHTLx21951; Wed, 24 Oct 2001 19:29:21 +0200 (MET DST) (envelope-from paulz@trantor.xs4all.nl) Message-Id: <200110241729.f9OHTLx21951@trantor.xs4all.nl> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Thomas Quinot Cc: Paul van der Zwan , current@freebsd.org, paulz@trantor.xs4all.nl Subject: Re: Multiple NFS server problems with Solaris 8 clients In-Reply-To: Message from Thomas Quinot of "Fri, 19 Oct 2001 18:31:02 +0200." <20011019183102.A20555@cosette.enst.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Wed, 24 Oct 2001 19:29:21 +0200 From: Paul van der Zwan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20011019183102.A20555@cosette.enst.fr>, Thomas Quinot wrote: >Le 2001-10-14, Paul van der Zwan =E9crivait : > >> I am using -current box as a homedir server for my Solaris clients and= >> have noticed a wierd problem. > >Other problems here, with Solaris 2.[68] as clients, and -CURRENT of >yesterday as server. ls works, but ls -l issues a 'NFS getacl failed' >message *and* waits for a timeout once for each file in the directory. > >The server is not multi-homed, and a packet capture shows no trace of >address mismatch problems. One interesting thing is that the client >first does GETATTR on the file (and apparently gets a reply), and >then sends some other RPC, to which the server never replies. >Could this be the getacl request mentioned in the client error message? >I see no mention of getacl whatsoever in the -CURRENT server code. If >no such function is implemented, shouldn't we reject the request? > >A packet capture is available at > http://www.infres.enst.fr/~quinot/nfs.cap > >Client is 137.194.192.1, server is 137.194.162.11. The test consists >in first performing an 'ls' on one file, then an 'ls -l' on the same >file. Result: > >ls photos-ta; ls -l photos-ta >photos-ta >NFS getacl failed for server shalmaneser.enst.fr: error 5 (RPC: Timed >out) >-rw------- 1 quinot astre 474 Oct 18 14:17 photos-ta I have looked at a trace I made using snoop and it shows an NFS_ACL call = which is not supported by FreeBSD. It should have sent a reply that it does not= know the NFS_ACL protocol but apparently it does not. = The only return traffic I see is an empty packet with the tcp ACK. It looks like an implementation error in the -current NFS server. Paul -- = Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message