From owner-freebsd-commit Tue Jun 27 12:57:56 1995 Return-Path: commit-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA00394 for commit-outgoing; Tue, 27 Jun 1995 12:57:56 -0700 Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA00381 for cvs-usrsbin-outgoing; Tue, 27 Jun 1995 12:57:39 -0700 Received: from FileServ1.MI.Uni-Koeln.DE (FileServ1.MI.Uni-Koeln.DE [134.95.212.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA00373 ; Tue, 27 Jun 1995 12:57:36 -0700 Received: by FileServ1.MI.Uni-Koeln.DE id AA03469 (5.67b/IDA-1.5); Tue, 27 Jun 1995 21:57:33 +0200 Message-Id: <199506271957.AA03469@FileServ1.MI.Uni-Koeln.DE> From: esser@zpr.uni-koeln.de (Stefan Esser) Date: Tue, 27 Jun 1995 21:57:33 +0200 In-Reply-To: esser (Stefan Esser) "Re: cvs commit: src/usr.sbin/pstat pstat.c" (Jun 27, 21:10) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Doug Rabson Subject: Re: cvs commit: src/usr.sbin/pstat pstat.c Cc: Doug Rabson CVS-commiters@freefall.cdrom.com, cvs-usrsbin@freefall.cdrom.com Sender: commit-owner@FreeBSD.org Precedence: bulk On Jun 27, 21:10, Stefan Esser wrote: } Subject: Re: cvs commit: src/usr.sbin/pstat pstat.c } On Jun 27, 4:07, Doug Rabson wrote: } } Subject: cvs commit: src/usr.sbin/pstat pstat.c } } } Log: } } Changes to support version 3 of the NFS protocol. } } The version 2 support has been tested (client+server) against FreeBSD-2.0, } } IRIX 5.3 and FreeBSD-current (using a loopback mount). The version 2 support } } is stable AFAIK. } } The version 3 support has been tested with a loopback mount and minimally } } against an IRIX 5.3 server. It needs more testing and may have problems. } } I have patched amd to support the new variable length filehandles although } } it will still only use version 2 of the protocol. } } Tried to access a DEC Alpha using the patched NFS code, } and get a panic: } } panic: allocbuf: page changed offset??!!!? Following up to my own message: NFS to a DEC Alpha (OSF/1 V3.0) works fine, if the "-3" option is given. I.e. the panic only happens, if a standard version 2 NFS mount is used, the version 3 works reliable and I can see the accesses tallied (using "nfsstat" on the Alpha, which offers seperate statistics for protocol version 2 and version 3). (BTW: Seems I've got the only NFS3 client here ... :) So, a NFS3 mount with no options will make a FreeBSD client panic, while a mount request with -3 specified seems to work fine. Regards, STefan -- Stefan Esser Internet: Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln FAX: +49 221 4705160 Weyertal 80 50931 Koeln