From owner-freebsd-current  Fri May  7  7:20:25 1999
Delivered-To: freebsd-current@freebsd.org
Received: from home.dragondata.com (home.dragondata.com [204.137.237.2])
	by hub.freebsd.org (Postfix) with ESMTP id C15FF14F8A
	for <current@FreeBSD.ORG>; Fri,  7 May 1999 07:20:19 -0700 (PDT)
	(envelope-from toasty@home.dragondata.com)
Received: (from toasty@localhost)
	by home.dragondata.com (8.9.2/8.9.2) id JAA05761;
	Fri, 7 May 1999 09:20:11 -0500 (CDT)
From: Kevin Day <toasty@home.dragondata.com>
Message-Id: <199905071420.JAA05761@home.dragondata.com>
Subject: Re: -current deadlocks within 5 mins, over NFS
In-Reply-To: <199905070817.DAA15632@home.dragondata.com> from Kevin Day at "May 7, 1999  3:17:46 am"
To: toasty@home.dragondata.com (Kevin Day)
Date: Fri, 7 May 1999 09:20:09 -0500 (CDT)
Cc: dillon@backplane.com, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 
> Matt, I told you about this before, but completely forgot about it. After
> doing considerable testing on my test servers, i thought -current was safe
> enough to try on our production shell servers. I installed -current on one
> of my servers, and to my dismay, it hung. :)
> 
> Within 5 minutes of running, nearly every process is blocked on 'inode',
> with the exception of a single 'cp' stuck in vmopar.
> 


Just to add more to this, before someone replies. Ran all night, still
hasn't crashed. On my test system, if I add that cron job back, it dies
very quickly, so this shouldn't be hard to reproduce to someone who needs
it.

-current sources grabbed last night.


Kevin


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message