From owner-freebsd-stable@FreeBSD.ORG  Tue May 27 09:04:43 2003
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id BF93A37B407
	for <stable@freebsd.org>; Tue, 27 May 2003 09:04:43 -0700 (PDT)
Received: from hub.org (hub.org [64.117.225.220])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CEE7043F85
	for <stable@freebsd.org>; Tue, 27 May 2003 09:04:41 -0700 (PDT)
	(envelope-from scrappy@hub.org)
Received: from portoclub.gr (unknown [64.117.225.220])
	by hub.org (Postfix) with ESMTP
	id 5FAF76BC62F; Mon, 26 May 2003 12:37:21 -0300 (ADT)
Date: Mon, 26 May 2003 12:37:21 -0300 (ADT)
From: "Marc G. Fournier" <scrappy@hub.org>
To: Mike Harding <mvh@ix.netcom.com>
In-Reply-To: <1053929957.7831.2.camel@netcom1.netcom.com>
Message-ID: <20030526123617.D56519@hub.org>
References: <20030521171941.364325314@netcom1.netcom.com>
	<20030524190051.R598@hub.org>
	<1053929957.7831.2.camel@netcom1.netcom.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: stable@freebsd.org
Subject: Re: system slowdown - vnode related
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 27 May 2003 16:04:44 -0000

On Mon, 25 May 2003, Mike Harding wrote:

> I'm running a very recent RELENG-4 - but I had a suspicion that this was
> unionfs related, so I unmounted the /usr/ports union mounts under a jail
> in case this was causing the problem, and haven't seen the problem
> since.  It's possible I accidently reverted to 4.8 when I built a
> release, but I don't see how...

'K, I wouldn't touch anything less then 4.8-STABLE ... the last set of
vnode related patches that I'm aware of were made *post* 4.8-RELEASE,
which, I believe, won't be included in RELENG-4 ...