From owner-freebsd-current Fri May 7 9:49:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id AA07814D0F for ; Fri, 7 May 1999 09:49:50 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA45656; Fri, 7 May 1999 09:49:36 -0700 (PDT) (envelope-from dillon) Date: Fri, 7 May 1999 09:49:36 -0700 (PDT) From: Matthew Dillon Message-Id: <199905071649.JAA45656@apollo.backplane.com> To: Kevin Day Cc: current@FreeBSD.ORG Subject: Re: -current deadlocks within 5 mins, over NFS References: <199905070817.DAA15632@home.dragondata.com> 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. : :I have a very silly, *very* poorly written script i run out of cron, every :10 mins or so, to update my passwd and group files. : :#/bin/sh :... : :What more info do you need for help in debugging this? : :Kevin This is great! Just what I've been looking for! I'll try to reproduce the lockup today. If it is stuck in vmopar I already have a good idea about what is going on. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message