From owner-freebsd-current Fri May 7 1:17:52 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 8AAB315366 for ; Fri, 7 May 1999 01:17:50 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id DAA15632; Fri, 7 May 1999 03:17:47 -0500 (CDT) From: Kevin Day Message-Id: <199905070817.DAA15632@home.dragondata.com> Subject: -current deadlocks within 5 mins, over NFS To: dillon@backplane.com Date: Fri, 7 May 1999 03:17:46 -0500 (CDT) Cc: 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. 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 cp /home/private/passwd /etc cp /home/private/master.passwd /etc cp /home/private/group /etc rm /etc/spwd.db.tmp >/dev/null 2>&1 pwd_mkdb /etc/master.passwd This script is the only source of a 'cp' anywhere... If I turn this off, I was able to run for at least 30 mins(more, if i hadn't rebooted) /home is a UDP NFS2 mount. Moving the source of those cp's to a local drive also fixes the problem, but breaks the use for my script. :) What more info do you need for help in debugging this? Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message