From owner-freebsd-questions@FreeBSD.ORG Tue Nov 25 05:46:06 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DCB016A4CE for ; Tue, 25 Nov 2003 05:46:06 -0800 (PST) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBFE243FDD for ; Tue, 25 Nov 2003 05:46:05 -0800 (PST) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from be-well.no-ip.com ([66.30.200.37]) by comcast.net (rwcrmhc11) with ESMTP id <2003112513460501300j3ciae>; Tue, 25 Nov 2003 13:46:05 +0000 Received: by be-well.no-ip.com (Postfix, from userid 1147) id C87606C; Tue, 25 Nov 2003 08:46:04 -0500 (EST) Sender: lowell@be-well.ilk.org To: "Marcel de Reuver" References: <000201c3b289$c921b900$6b0aa8c0@helpman.local> From: Lowell Gilbert Date: 25 Nov 2003 08:46:04 -0500 In-Reply-To: <000201c3b289$c921b900$6b0aa8c0@helpman.local> Message-ID: <448ym4pnmr.fsf@be-well.ilk.org> Lines: 16 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-questions@freebsd.org Subject: Re: NFS mount problems X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Nov 2003 13:46:06 -0000 "Marcel de Reuver" writes: > I moved a RedHat Linux box for obvious reasons to FreeBSD v5.1 > It is main job for that box is act like a mailhub. Also it servers Windows > clients as a Samba server. There are two NFS mounts of a HP-UX workstation. > With RedHat no problems, with FreeBSD noting but trouble with these mounts. > Even the box is rebooting itself.... The official recommendation for a mailhub would be to run FreeBSD 4.9 rather than 5.1, but I'll assume you needed 5.1 for some specific reason. You'll definitely need to give more information on the symptoms; something useful is probably in the logs, for example. But you may need to go to the -CURRENT mailing list if this problem is specific to FreeBSD 5.x.