From owner-freebsd-questions@FreeBSD.ORG Tue Oct 5 05:22:52 2004 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 0839416A4CE for ; Tue, 5 Oct 2004 05:22:52 +0000 (GMT) Received: from smtp16.wxs.nl (smtp16.wxs.nl [195.121.6.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE8F943D41 for ; Tue, 5 Oct 2004 05:22:51 +0000 (GMT) (envelope-from freebsd@akruijff.dds.nl) Received: from kruij557.speed.planet.nl (ipd50a97ba.speed.planet.nl [213.10.151.186]) by smtp16.wxs.nl (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0I53000UXIY2BZ@smtp16.wxs.nl> for freebsd-questions@freebsd.org; Tue, 05 Oct 2004 07:22:50 +0200 (CEST) Received: from alex.lan (localhost [127.0.0.1]) by kruij557.speed.planet.nl (8.12.10/8.12.10) with ESMTP id i955MoMP001299; Tue, 05 Oct 2004 07:22:50 +0200 Received: (from akruijff@localhost) by alex.lan (8.12.10/8.12.10/Submit) id i955MngE001298; Tue, 05 Oct 2004 07:22:49 +0200 Content-return: prohibited Date: Tue, 05 Oct 2004 07:22:49 +0200 From: Alex de Kruijff In-reply-to: <20041004001747.J10913@ganymede.hub.org> To: "Marc G. Fournier" Message-id: <20041005052249.GC917@alex.lan> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: Mutt/1.4.2.1i References: <20041004001747.J10913@ganymede.hub.org> X-Authentication-warning: alex.lan: akruijff set sender to freebsd@akruijff.dds.nl using -f cc: freebsd-questions@freebsd.org Subject: Re: nfs server not responding / is alive again X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Oct 2004 05:22:52 -0000 On Mon, Oct 04, 2004 at 12:22:30AM -0300, Marc G. Fournier wrote: > > I'm using an nfs mount to get at the underlying file system on a system > that uses unionfs mounts ... instead of using nullfs, which, last time I > used it over a year ago, caused the server to crash to no end ... > > But, as soon as there is any 'load', I'm getting a whack of: > > Oct 3 22:46:16 neptune /kernel: nfs server neptune.hub.org:/vm: not > responding > Oct 3 22:46:16 neptune /kernel: nfs server neptune.hub.org:/vm: is alive > again > Oct 3 22:48:30 neptune /kernel: nfs server neptune.hub.org:/vm: not > responding > Oct 3 22:48:30 neptune /kernel: nfs server neptune.hub.org:/vm: is alive > again > > in /var/log/messages ... > > I'm running nfsd with the standard flags: > > nfs_server_flags="-u -t -n 4" > > Is there something that I can do to reduce this problem? increase number > of nfsd processes? force a tcp connection? You could try giving the nfsd processes more priority as root with rtprio. If the file /var/run/nfsd.pid exist then you could try something like: rtprio 10 -`cat /var/run/nfds.pid`. You could also try giving the other porcesses less priority like nice -n 2 rsync. But i'm am not show how this works at the other end. > The issue is more prevalent when I have >4 processes trying to read from > the nfs mounts ... should there be one mount per process? the process(es) > in question are rsync, if that helps ... they tend to be a bit more 'disk > intensive' then most processes, which is why I thought of increasing -n > ... I think you're problem is not that you disk is used havely but that you're NIC (rsync kinda does that) is. The warnings you get indicate that you're computer can't get a responce from you're server. It acts normaly as soon as it can. Why do you have rsync sync mounted nfs disks? -- Alex Articles based on solutions that I use: http://www.kruijff.org/alex/FreeBSD/