Date: Fri, 7 May 1999 09:20:09 -0500 (CDT) From: Kevin Day <toasty@home.dragondata.com> To: toasty@home.dragondata.com (Kevin Day) Cc: dillon@backplane.com, current@FreeBSD.ORG Subject: Re: -current deadlocks within 5 mins, over NFS Message-ID: <199905071420.JAA05761@home.dragondata.com> In-Reply-To: <199905070817.DAA15632@home.dragondata.com> from Kevin Day at "May 7, 1999 3:17:46 am"
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905071420.JAA05761>