From owner-freebsd-stable Mon Aug 17 12:02:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23797 for freebsd-stable-outgoing; Mon, 17 Aug 1998 12:02:51 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.fcc.net (241.pearlriver.fcc.net [207.198.253.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23787 for ; Mon, 17 Aug 1998 12:02:49 -0700 (PDT) (envelope-from nathan@fcc.net) Received: from noc.fcc.net (nathan@noc.fcc.net [207.198.253.18]) by mail.fcc.net (8.9.1/8.9.1) with ESMTP id PAA09295 for ; Mon, 17 Aug 1998 15:01:40 -0400 (EDT) Received: (from nathan@localhost) by noc.fcc.net (8.9.1/8.9.1) id PAA17768 for freebsd-stable@FreeBSD.org; Mon, 17 Aug 1998 15:02:55 -0400 (EDT) Message-ID: <19980817150255.A17575@fcc.net> Date: Mon, 17 Aug 1998 15:02:55 -0400 From: Nathan Dorfman To: freebsd-stable@FreeBSD.ORG Subject: NFS problems in -stable? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In 2.2.7-R as well as 2.2.7-S built an hour or so ago, I'm having problems with nfs. The FreeBSD machine is running mountd, and exporting /usr/home; two Solaris machines are mounting this home directory. The server randomly stops responding when I try to do things such as gunzip, tar xf, and install. This seems to happen whether or not the operation spans remote/local mountpoints. As I've been told that only NFSv3 is broken, I'm running mountd -2 and have -o vers=2 on the Solaris client. The problem seems to come up mostly from the 2.5.1 machine. I haven't run into it on 2.6, but that machine hardly gets used. Does anyone know if this is some pilot error, broken solaris, or broken FreeBSD? -- Nathan Dorfman | E-mail: nathan@fcc.net Frontline Communications | Front desk: 914-623-8553: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message