From owner-freebsd-hackers Tue Nov 16 11:44:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from usc.edu (usc.edu [128.125.253.136]) by hub.freebsd.org (Postfix) with ESMTP id 5CE1D14D9C for ; Tue, 16 Nov 1999 11:44:14 -0800 (PST) (envelope-from walker@usc.edu) Received: from skat.usc.edu (walker@skat.usc.edu [128.125.253.131]) by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id LAA04749 for ; Tue, 16 Nov 1999 11:44:13 -0800 (PST) Received: from localhost (walker@localhost) by skat.usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id LAA19170 for ; Tue, 16 Nov 1999 11:44:12 -0800 (PST) Date: Tue, 16 Nov 1999 11:44:12 -0800 (PST) From: Mike Walker To: freebsd-hackers@FreeBSD.ORG Subject: Re: vmpfw in pine via NFS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I am noticing a large number of pine (and only pine) procs stuck in >> disk-wait. All of the are in the WCHAN "vmpfw". Any ideas what >> this may mean? > Is the mail spool pine accessing on this NFS volume, or just the > binary? > > If so you're breaking the cardinal rule of NFS: Never serve mail > spools via NFS. > > Doug White | FreeBSD: The Power to Serve > dwhite@resnet.uoregon.edu | www.FreeBSD.org Why is this a cardinal rule? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message