From owner-freebsd-questions Wed Dec 8 6:45: 7 1999 Delivered-To: freebsd-questions@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id 786FF15524 for ; Wed, 8 Dec 1999 06:44:28 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991207212354.03516@mojave.sitaranetworks.com> Date: Tue, 7 Dec 1999 21:23:54 -0500 From: Greg Lehey To: Rob Hunter , freebsd-questions@FreeBSD.ORG Subject: Re: machine hangs while accessing nfs share Reply-To: Greg Lehey References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: ; from Rob Hunter on Tue, Dec 07, 1999 at 03:55:35PM +0200 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 7 December 1999 at 15:55:35 +0200, Rob Hunter wrote: > Hi > > I'm having a bit of a problem with an nfs share I'm moving files to. Every > time I start moving them, the box dies within between 1 and 3 minutes. Which box? How does it die? In the subject line you say "hang". > I've tried mounting it as follows: > > mount_nfs -o intr,soft some.machine.where.it's.shared:/vol/share > /destination > > I've also tried using the following: > > nfsv2 > nfsv3 > mntudp > > and also with plain old: > > mount_nfs some.machine.where.it's.shared:/vol/share /destination > > I've tried grabbing the latest source for stable (which is now 3.4rc) and > still, the machine just hangs after a while. This is when I'm moving files > off a local disk and onto the share..... Is the server machine multi-homed (i.e. does it have more than one IP address?). If so, can you try mounting with the IP address by which you access it, and see if it still hangs. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message