From owner-freebsd-current Tue Nov 6 15:29:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail11.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by hub.freebsd.org (Postfix) with ESMTP id 2904A37B405 for ; Tue, 6 Nov 2001 15:29:33 -0800 (PST) Received: (qmail 79160 invoked from network); 6 Nov 2001 23:29:31 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 6 Nov 2001 23:29:31 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 06 Nov 2001 15:29:31 -0800 (PST) From: John Baldwin To: current@FreeBSD.org Subject: NFS locking and 4.x and 5.x 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 Apparently trying to mix NFS clients and servers of different versions seems to be unsupported if file locks are used. :( I have been attempting to build a 5.0 release over NFS with a 4.4-STABLE server. During release, we do a pwd_mkdb which tries to lock the password file. This has caused me no end of trouble. At first, I just had nfsiod on the client, and nfsd, mountd, and rpc.statd on the server as this is how rc.network currently does things. Apparently, when the new locking code was added, it became necessary to run rpc.lockd and rpc.statd on the client (and rpc.lockd on the server), but rc.network was never updated for this. So at first pwd_mkdb kept failing with 'Operation not supported'. Now that I have rpc.lockd and rpc.statd running on both client and server, pwd_mkdb hangs in the 'lockd' wait state: ===> monthly install -c -o root -g wheel -m 755 200.accounting 999.local /home/john/work/release/etc/periodic/monthly install -c -o root -g wheel -m 0644 /usr/src/gnu/usr.bin/send-pr/categories /home/john/work/release/etc/gnats/freefall rm -f /home/john/work/release/etc/termcap ln -s /usr/share/misc/termcap /home/john/work/release/etc/termcap rm -f /home/john/work/release/etc/rmt ln -s /usr/sbin/rmt /home/john/work/release/etc/rmt load: 0.00 cmd: pwd_mkdb 19087 [lockd] 0.00u 0.02s 0% 832k load: 0.00 cmd: pwd_mkdb 19087 [lockd] 0.00u 0.02s 0% 832k load: 0.00 cmd: pwd_mkdb 19087 [lockd] 0.00u 0.02s 0% 832k load: 0.00 cmd: pwd_mkdb 19087 [lockd] 0.00u 0.02s 0% 832k load: 0.00 cmd: pwd_mkdb 19087 [lockd] 0.00u 0.02s 0% 832k load: 0.00 cmd: pwd_mkdb 19087 [lockd] 0.00u 0.02s 0% 832k load: 0.00 cmd: pwd_mkdb 19087 [lockd] 0.00u 0.02s 0% 832k ^C ---------------------------------------- release started at 15:04:33 on 11/06/01 release died at 15:22:12 on 11/06/01 ---------------------------------------- Thus it seems impossible to build a 5.0 release over NFS with a 4.x client. Can we maybe have a mount option to disable locks on the client, or just do something to fix NFS please? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message